Re:High-Performance server for NATS.io, the cloud and edge n...
by bzzzt on Monday July 24, 2023 @08:14AM
(#36846669)
Just like you don't want to support tens of different databases you shouldn't build your solution on lots of bridged message busses. If stuff goes down at 2 am you don't want to have to find out which message queue was the problem or what tooling you should use to debug it.
Re:High-Performance server for NATS.io, the cloud and edge n...
by Kinrany on Monday July 24, 2023 @08:56AM
(#36847242)
Sure, but it's an inconvenience, not a total blocker. With databases you lose foreign keys and you have to replace a single query with N. And you don't want to have ten different solutions of course, but two is fine and allows for comfortable migrations.
And even NATS Streaming still works: it is deprecated, not removed.
Unlike databases, a good thing about messaging and streaming solutions is that you don't have to pick one: you can make them talk to each other as long as there are bridges. This also applies to different approaches to messaging/streaming provided by a single platform.