As our applications and services grow and we start to break more into Microservices a key part of building applications is Messaging. Being able to pass messages between the applications quickly becomes critical to our service.
Over the next few blog posts I'll look at getting started with different messaging systems and how to use them. It's not a compare it's a getting started in each of them.
Why do we need messaging
Messaging allows communication between applications. For example we create a user in our database and then create a message onto our message bus. Our email service is listening to the message bus. Gets the new message and sends the welcome email. We've now wired two applications to work together over a message bus.
Microservices is a particular way of designing software applications as suites of independently deployable services. In a microservices world communication between applications has to be robust and scalable. Message buses provide a flexible solution to this. We can create services and deploy them in different places. You can even have services in different languages, once they can read the same message bus they can do what they need to do.
Over the next few posts I'll introduce different Message bus services and providers.