11 ms·
I don't have much experience with RabbitMQ, but I don't fully agree with your point about ES. We run a cluster for ingesting logs, and it's much cheaper. The c
by vladvasiliu 4y ago
I don't have much experience with RabbitMQ, but I don't fully agree with your point about ES.
We run a cluster for ingesting logs, and it's much cheaper. The clustering part is basically painless. I had to script a bunch of things to easily change instance sizes (adjust the memory according to available RAM), and that's it. Sure, if you don't want to have to deal with this, going the managed route is OK.
The most issues we've had, however, is with the actual documents sent for indexing, querying them, etc. So basically something with which ES Cloud, or other managed solution, wouldn't have helped.
I'd expect RMQ to be roughly the same. I've seen a bunch of people do weird things shoveling messages from left to right and not consuming them before the RAM exploded. All this on managed RMQ.
- mst 4y agoI think "use a managed service until that starts to suck" is often not a bad heuristic - with a bit of luck by the time (if ever) it does start to suck you'll be familiar enough with the system that spinning up your own cluster will involve significantly less "learning the hard way" than it would've done had you done it first off. And I say this as somebody who really really dislikes managed services from a "but I want to have total control" point of view (this is not entirely rational on my part but true of me nonetheless.)