Kafka in scenario with many devices/data consumers -


currently evaluating apache kafka use case have (up to) several thousand devices produce transactions - each 1 generating response in back-end. response, must go originating device.

for subscriptions, then, seems have choice of either having topic per device (awkward management standpoint), or single topic transaction responses, , have each device pull down data topic - including meant else (sub-optimal performance-standpoint).

is there way have brokers somehow filter data in polling process (on kafka side)? seems me common requirement, far haven't seen along lines.


Comments

Popular posts from this blog

android - InAppBilling registering BroadcastReceiver in AndroidManifest -

python Tkinter Capturing keyboard events save as one single string -

sql server - Why does Linq-to-SQL add unnecessary COUNT()? -