If somebody insists on using Kafka as a database you might be able to do the 
following:

1. Create a "compacted topic".   The key for the topic should be the  point of 
sales id.
2. Create a webservice which takes a point of sale id and can read or update 
the topic
3. Have the point of sale apps periodically call the webservice


This won't work if the price list is truly a stream of things rather than "just 
get the latest list".

-Dave

On 3/31/19, 7:01 PM, "Peter Bukowinski" <pmb...@gmail.com> wrote:

    I don’t want to be a downer, but because kafka is relatively new, the 
reference material you seek probably doesn’t exist. Kafka is flexible and can 
be made to work in many different scenarios — not all of the ideal.

    It sounds like you’ve already reached a conclusion that kafka is the wrong 
solution for your requirements. Please share with us the evidence that you used 
to reach this conclusion. It would be helpful if you described the technical 
problems you encountered in your experiments so that others can give their 
opinion on whether can can be resolved or whether they are deal-breakers.

    --
    Peter

    > On Mar 31, 2019, at 4:24 PM, <akute...@gmail.com> <akute...@gmail.com> 
wrote:
    >
    > Hello!
    >
    >
    >
    > I ask for your help in connection with the my recent task:
    >
    > - Price lists are delivered to 20,000 points of sale with a frequency of 
<10
    > price lists per day.
    >
    > - The order in which the price lists follow is important. It is also
    > important that the price lists are delivered to the point of sale online.
    >
    > - At each point of sale, an agent application is deployed, which processes
    > the received price lists.
    >
    >
    >
    > This task is not particularly difficult. Help in solving the task is not
    > required.
    >
    >
    >
    > The difficulty is that Kafka in our company is a new "silver bullet", and
    > the project manager requires me to implement the following technical
    > decision:
    >
    > deploy 20,000 Kafka consumer instances (one instance for each point of 
sale)
    > for one topic partitioned into 20,000 partitions - one partition per
    > consumer.
    >
    > Technical problems obtained in experiments with this technical decision do
    > not convince him.
    >
    >
    >
    > Please give me references to the books/documents/blogposts. which clearly
    > shows that Kafka not intended for this way to use (references to other
    > anti-patterns/pitfalls will be useful).
    >
    > My own attempts to find such references were unsuccessful.
    >
    >
    >
    > Thank you!
    >
    >
    >



This e-mail and any files transmitted with it are confidential, may contain 
sensitive information, and are intended solely for the use of the individual or 
entity to whom they are addressed. If you have received this e-mail in error, 
please notify the sender by reply e-mail immediately and destroy all copies of 
the e-mail and any attachments.

Reply via email to