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
Thanks, Vincent!
Yes, i totally agree about coupling/decoupling. The need for the producer
to send messages to a specific partition and the consumer to consume from a
specific partition creates high coupling between them. So in the future
changing the topic partitioning scheme will be impossible w
Thanks, Dmitry.
It seems your solution is the the most appropriate for me, because the
reasons why consumers (POS terminals) will be added/removed are different
from the reasons why partitions will be added/removed.
I think that topic division to partitions and POS terminals division to
logical g
Maybe you can find some litterature about messaging patterns ?
Usually, a single kafka topic is used to do PubSub pattern, i.e decoupling
producers and consumers.
In your case, it seems that the situation is quite coupled, i.e you need to
generate and send 20k price lists to 20k specific consumers
Going off of what Hans mentioned, I don't see any reason for 200,000
partitions...you don't need one partition per POS. You can have all of your
pos listening to one partition and each pos agent having a unique group
id. The POS agent only processes the messages that are relevant to him,
and simpl
Yes but you have more than 1 POS terminal per location so you still don't need
20,000 partitions. Just one per location. How many locations do you have?
In doesn’t matter anyway since you can build a Kafka cluster with up to 200,000
partitions if you use the latest versions of Kafka.
https://bl
Thanks, Hans!
We use location specific SKU pricing and send specific price lists to the
specific POS terminal.
пн, 1 апр. 2019 г., 3:01 Hans Jespersen :
> Doesn’t every one of the 20,000 POS terminals want to get the same price
> list messages? If so then there is no need for 20,000 partitions.
>
Yes, we have location specific SKU pricing.
пн, 1 апр. 2019 г., 4:08 Steve Howard :
> Do you have location specific SKU pricing?
>
> On Sun, Mar 31, 2019, 7:25 PM
> > Hello!
> >
> >
> >
> > I ask for your help in connection with the my recent task:
> >
> > - Price lists are delivered to 20,000 p
Do you have location specific SKU pricing?
On Sun, Mar 31, 2019, 7:25 PM 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 fol
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
solu
Doesn’t every one of the 20,000 POS terminals want to get the same price list
messages? If so then there is no need for 20,000 partitions.
-hans
> On Mar 31, 2019, at 7:24 PM, wrote:
>
> Hello!
>
>
>
> I ask for your help in connection with the my recent task:
>
> - Price lists are delive
11 matches
Mail list logo
