RabbitMQ vs. Kafka – An Architect’s Dilemma (Part 1)
I've seen Tibco Rendezvous used in manufacturing. ~300 megabytes per hour of raw log generated 24/7/365 by tools and control systems in a factory setting. Probably on the order of 10k+ participants in the pub/sub network.<p>If you are running something like a factory where thousands of independent systems need to communicate in some way, this kind of tech starts to look like the <i>only</i> option.<p>If you are orchestrating the concerns of 5-10 services, I think you are making your life harder than it needs to be with ESB-style abstractions. Direct method invocation is much more reliable than whatever any one of these vendors could ever sell you. Put all your services into one exe. If you can't be bothered to use one language/repo, there are <i>still</i> ways to achieve this.<p>The real architect's dilemma is shoving one's edifice-constructing ego into a box long enough to produce a useful shack for the business.