Microservices and Message Queues - Explained

It's time to take a closer look at Microservices and Message Queueing to uncover the benefits of this architecture.

We will use an application where users can upload and rank each other's photos as an example. In the first version everything is built into a single system, with highly coupled functionality. This is often referred to as a monolithic application. And as we will learn, this approach has many downsides. Especially when it comes to performance, reliability, scaling, and maintenance.

A much better architecture is to divide the functionality of the app into separate microservices. And in order for this to work, we need to use a Message Queue as a broker. The Message Queue will manage all communication between the different services. Some of the benefits mentioned today are:

- A micro service architecture makes your application highly scalable.
- Low coupling between parts leads to easier development and maintenance.
- The different micro services can be written in different languages
- Fault isolation is achieved. The app is still accessible even if one part of the system is down temporarily.

CloudAMQP is the largest hosting provider of the open source message broker - RabbitMQ. Try it free - https://www.cloudamqp.com

New to RabbitMQ? What is RabbitMQ?
Our blog series "RabbitMQ for beginners" is the perfect introduction - https://www.cloudamqp.com/blog/2015-05-18-part1-rabbitmq-for-beginners-what-is-rabbitmq.html
Or download our popular and free RabbitMQ Ebook - https://www.cloudamqp.com/rabbitmq_ebook.html

Видео Microservices and Message Queues - Explained канала CloudAMQP