{"id":744,"date":"2022-01-18T16:46:29","date_gmt":"2022-01-18T13:16:29","guid":{"rendered":"https:\/\/m-shaeri.ir\/blog\/?p=744"},"modified":"2022-03-24T17:43:06","modified_gmt":"2022-03-24T13:13:06","slug":"a-simple-real-world-project-with-rabbitmq-python-java-and-php","status":"publish","type":"post","link":"https:\/\/mshaeri.com\/blog\/a-simple-real-world-project-with-rabbitmq-python-java-and-php\/","title":{"rendered":"RabbitMQ + Java + Python + PHP Real-World Example"},"content":{"rendered":"\n

RabbitMQ<\/strong> is one of the most popular and easy to deploy message brokers. It receives messages from producers, and delivers them to consumers. It is used to reduce loads and delivery times in applications, and it is widely used in microservice architectures to facilitate asynchronous communication between services. One thing that makes this message broker very popular is that for all the major programming languages, the client libraries to work with the RabbitMQ are available and easy to use. In this article I am going to build a simple project in which different services with different technology communicate to each other via RabbitMQ.<\/p>\n\n\n\n

Project Description<\/h2>\n\n\n\n

We want to build a registration system that sends SMS & email confirmation messages to user after registration. We have 3 tasks to be done in registration process : <\/strong>recording user information in database<\/span>, sending SMS confirmation<\/span> and sending email confirmation<\/span>. <\/p>\n\n\n\n

Monolith approach<\/span><\/h2>\n\n\n\n

The simplest approach for implementing this system is to do all tasks in sequence and synchronously as a monolith application. In this way, first we store user information in database, then, after completion of first step we send SMS message to user by calling external 3dparty API and wait for its response, next we call the email function to send confirmation email and wait for the function to return the result, finally we can show the success message to user in the browser. <\/p>\n\n\n\n

\"\"<\/a>
Sequential approach for registration system<\/figcaption><\/figure><\/div>\n\n\n\n

One of disadvantages of this approach is that user will face with an unexpected delay in the situation that any of SMS API or email function takes more time to respond. Moreover, if for any reason the system fail just after first step (storing data in database), no SMS and no email message will be sent to user, because all the next tasks depend to completion of first one .<\/p>\n\n\n\n

Separated services with asynchronous inter-communication<\/span><\/h2>\n\n\n\n

Separated services allows a system to be divided into a number of smaller, independent and loosely coupled parts. Each part is only responsible for its own tasks , particularly in microservice architecture each service has got exclusive and isolated resources. They work as autonomous processes and communicate with each other through APIs which can be in synchronous or asynchronous way. In this section I focus on asynchronous way of communicating. Each service can be implemented in a different programming language and technology on a different platform.<\/p>\n\n\n\n

The Registration System as I described above consists of 3 main parts : recording user information in database<\/span>, sending SMS confirmation<\/span> and sending email confirmation<\/span>. We simply assign each task to an individual service with same name.<\/p>\n\n\n\n

\"\"<\/a>
Turning monolith project into number of Individual Independent Services<\/figcaption><\/figure><\/div>\n\n\n\n

As it is crystal clear,<\/p>\n\n\n\n