Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

i’d love to hear some Kafka as a database success/horror stories. What’s the general consensus?


It works well with master data [1], i.e. semi-static data of limited volume that is widely needed throughout systems. Think physical store locations and such.

Services can either store it in their own database and still get an update stream, or services can read the complete set on boot and keep it in memory. It can avoid the need for RPC/REST calls so centralized services that keep track off this kind of data, preventing cascading failures if those fail.

[1] https://en.wikipedia.org/wiki/Master_data


It works great with the right kind of data.


What are the wrong kinds of data? It would be nice to know before I fall into a trap.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: