Continuing on my theme of message-oriented, I thought I’d get into a bit of detail about the various middleware options and some details about these options. Regardless of what type of middleware is chosen, one thing is common to all types of message-oriented middleware—the fact that they broker messages from producers to consumers. Impetus Before I get too far into the options, let’s look at a couple of the common reasons behind moving to a message-oriented architecture. One impetus towards MOM is to integrate various legacy or third-party systems into a new or exiting enterprise system. This type of MOM … Continue reading Enterprise Service Buses, Brokers, Message Queues, Oh My!
I recently blogged about Message-Oriented Architecture (and Message-Oriented Middleware, MOM). The technology leads to extremely flexible and scalable applications; but it really distracts from the system. It’s like calling a standard single-process application as Control-Unit Oriented Architecture. Sure, the application is divided into instructions that eventually make their way to the control unit of the CPU; but that’s not only a implementation detail of the application; it’s an essential implementation detail. It’s pretty hard to write an application that doesn’t eventually distil down to instructions given to a control unit of a CPU. And that’s kind of the problem with … Continue reading Message-Oriented Architecture is a Misleading Term
I’ve had a few people ask me about message-oriented architectures and my knowledge and experience of it has evolved over time; so, I figured it would be a good idea to collect and publish some information about it. It’s not one of those topics on the Internet that has gotten a lot of content, so I’ll try and change that. A Message-Oriented Architecture is sometimes called Message-Oriented Middleware or MOM because there’s a middle tier or middleware that acts as the broker to relay messages from producers to consumers. At the most succinct definition MOM is simply an architecture that … Continue reading Message-oriented Architectures (Updated)
Recently I’ve been doing a bit of work with queues, in part with RabbitMQ. Unfortunately, (or fortunately, depending on your point of view) network connections where I am have had a tendency to be unreliable. That’s a story for the pub; but, needless to say we needed our clients of RabbitMQ to be robust in light of disconnections. Fortunately, RabbitMQ has ways of dealing with this. A bit about queues Queues are a two way communication mechanism. You can enqueue messages and dequeue messages. In a distributed system you often have a local queue that you asynchronously deal with when … Continue reading Robustness with RabbitMQ in .NET