3 ms·
All right, that makes sense. It is likely that we'll see a peak in the 10s of thousands at a time, if that. Probably more as we move into the future. I want to
by lekker 10y ago
All right, that makes sense. It is likely that we'll see a peak in the 10s of thousands at a time, if that. Probably more as we move into the future.
I want to avoid deploying a piece of software now that we'll need to swap out in a year since it does not provide what we need anymore, though I suppose that is a natural part of scaling.
What would you recommend as an alternative to Kafka that does adequate real-time processing? The real-time-ness of it is important for our use-case. Maybe even some kind of time-series database system could work.
- baconomatic 10y agoWhat are you using right now to handle this load?
- krallistic 10y agoIf you really need "real-time-ness" TSDB will probably not work. You could go with sparkstreaming or flink but for that amount that will be overkill. Kafka scales quite nicely and is relativly easy to operate (compared to spark etc). But thats only if you really need to scale, for your current usage even kafka is a bit overkill.
- lekker 10y agoAll right, thank you. I'll look into the other options you mentioned