4 ms·
You put events in one end, and it distributes them, reliably and consistently, to distributed end-points that can consume them. That is far more powerful than s
by tcoppi 10y ago
You put events in one end, and it distributes them, reliably and consistently, to distributed end-points that can consume them. That is far more powerful than simply being used to log events for later retrieval, though it can be used for that. I have seen systems using Kafka that process tens of thousands of time-sensitive events a second and distribute them all over the world for independent processing as part of a larger system.
- toomuchtodo 10y ago"real-time event journaling and dissemination system"?
- tcoppi 10y agoYes I like that, much more accurate descriptor than "log", though it is more verbose. In the end it is really just nitpicking I guess, but the discoverability of calling these systems "log services" is very low compared to what they are really capable of.
- deleted 10y ago[deleted]
- Terr_ 10y agoSomehow I associate "journal" with temporary/transitional data, but that's probably just me thinking of journaling file-systems.
- toomuchtodo 10y agoWhen I think journal, I think a permanent record of rdbms transactions or perhaps even a blockchain. I agree with you though that the persistence of data needs to be defined when discussing a journal of any sorts.
- grogers 10y agoYou might prefer 'ledger' to emphasize the immutability of the journal.