• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Devaka Cooray
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Bear Bibeault
  • Paul Clapham
  • Knute Snortum
  • Rob Spoor
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Piet Souris
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Frits Walraven
  • Ganesh Patekar

Kafka Streams In Action: Topics and Limitation in Kalka systems

Ranch Hand
Posts: 77
Netbeans IDE Firefox Browser Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Dear Author,

Purchase Transaction Flow is being applied with Kalka System. Every record in each category that relates to a topic or topics. The below diagram 1.15 depicted the simplification of purchase order requirements with Kafka messaging system, even-sourcing and logs.

For instance, Kafka stream, i.e. purchaseKStream is being written on top of kafka based purchasing application.  While Jane Doe processes at a given time, there is the possibility for recording records over time.   As the problem domain or topics increases, the processor and child nodes will also be increased.

Would it be there any limitation for processors and nodes in DAC? How does it affect the computation time while the larger nodes are added?

Thank you
[Thumbnail for Fig1_15.png]
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Noorul,

I'm sure there is some limit to the number of processors you can add, but I don't have an idea of what that number is.  
As you add more processors, it will take more time for a record to work through the topology.

  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!