Microservices Architecture in Laravel

tufayalhossin
tufayalhossin
Tufayal Hossin Emon

  • The Riskiest Thing Is To Take No Risks.
  • Writen article 12
Microservices Architecture in Laravel

Here's what we've been up to recently.


Microservices Architecture in Laravel

In this article, I’ll create micro-services architecture for little online stores.


So we are visiting to build a web store app, within the application, users can list products available. It’s been products listed any user who signs up to our application should buy products, checkout, and make payment.


The architecture of micro-services is within the following diagram. Let’s have a glance and take a look at it to elucidate still.


In the above diagram overall design of the applying and application have events like user-created, user updated, product created, product updated, product add, order, payment etc.

our client interact with microservices and each is connected with a message broker called RabbitMQ


If a product add to the cart, product service invoked and update product status in MongoDB and RabbitMQ send a message to order service and build an order with payment status pending.


Now when the user made the payment, the payment service invoked and also the message broker (RabbitMQ) sends a message to the order service and updates the order payment status to finish in DB.


RabbitMQ may be a messaging broker — an intermediary for messaging. It gives your applications a typical platform to send and receive messages, and your messages a secure place to measure until received.


Further Resources For You

Here's what we've been up to recently.

View all