I've often heard wisdom like "it's irresponsible to use Kafka when you could just use RabbitMQ" but why does that statement not work equally well in the opposite direction?
It seems like some "you don't need this fad technology" sentiments don't provide a whole lot of justification for sticking with the unfashionable choice. Does it all come down to "the devil you know?" What if you aren't that experienced with either choice?
It could, in some circumstances. Generally, though, the two have only a very small overlap with respect to messaging use cases. One was designed to be general purpose and solve a variety of MQ use cases and serve even "dumb" clients. One was designed very specifically to impose a high burden of state tracking on clients for a very specific paradigm.
> It seems like some "you don't need this fad technology" sentiments don't provide a whole lot of justification for sticking with the unfashionable choice.
The "unfashionable choice" that works doesn't need justification. The new shiny one does.
Why? That's what I'm asking.
- More people who know how to operate it
- A greater portion of its failure modes that are known, with workarounds
- Mature tooling and libraries
New technologies need a compelling reason that their pros will outweigh the above incumbent benefits.
Yeah well that's a poor sales strategy. Being honest does not pay the rent.
There's also a lowest common denominator effect, where the other guy's marketing makes false claim X, and if your marketing doesn't, you are at a big disadvantage. Most of the time competitors aren't dumb enough to make a claim that is so blatantly false as to be legally actionable; as long as they steer clear of that high bar, they will make a lot of gains by making a misleading claim (note: they may make a lot of gains even if they can be held legally accountable, as that is a slow and expensive process, and the expected cost/penalty may fall far short of the expected profit).
1) Their product hasn't launched yet.
2) They desperately regret using Mongo and are trying to get rid of it.
Everything is a mind game. People have identified their use of things like Mongo as being on the forefront of a developing technology, it makes them feel important and interesting. Try taking that meaning away from them and see how it goes for you. The practicalities of actually using the thing hardly matter.
And is the guy who initially advocated for Mongo going to show up with his tail between his legs and admit he made a mistake? Nope, even if he wants to, that would be a big hit for him career-wise and after our mid-20s most of us have been disabused of our egalitarian notions and know better than to do that.
RethinkDB is the "good engineering" counter to MongoDB. Didn't oversell, worked hard to build a world-class product that targeted the same general product class. Compare for yourself and see what you get by proceeding with an engineering emphasis.
Marketing is mandatory, and developers are naive if they believe they or their field is immune.
The recent discussion between Sam Harris and Scott Adams might be interesting to you. Take into account that moral and good are synonymous with truth, to Sam Harris (strict rationalist) and Scott Adams is a consequentialist/utilitarian.
On the other hand when companies and maintainers are honest about the limitations it allows for a much easier conversation about how those limitations affect our products and how to trade off the mitigation approach and risk.
When the vendor claims there's no need for developers to use their brains they're all too eager to believe it.