If you want to move into Microservice Architecture, this course can help you with a practical examples.
Microservice architecture helps you to scale your product and make it more meaningful to add new features. Also your teams can be divided into smaller squads with ownership of respective domain. So its not only scaling your product but also teams around. Another important point is you will be able to easily bring new technologies with the help of message broker. We will see RabbitMQ mainly as an example but possible to pick and apply other solutions.
Here are some other benefits you can get from this course to apply your project.
* Easier to scale when high traffic hits your product, since you re removing the single point of failure from your architecture and using message broker with persistent storage feature. When your service is back, can start consuming the messages from where it left.
* Use Golang when you need and php in another, as long as you communicate with the same json structure, it won’t be problem.
What you’ll learn
- How to use RabbitMQ with Symfony.
- Be confident with Symfony Messenger compononent.
- How a simple Microservice works with a message broker.
- How to work with Kubernetes in Microservice environement.
Course Content
- Introduction –> 1 lecture • 4min.
- RabbitMQ and Game Service Setup –> 8 lectures • 43min.
- Guesses Service Setup and Implementation –> 6 lectures • 23min.
- Stats Service Setup and Implementation –> 3 lectures • 11min.
- Query Service Setup and Implementation –> 4 lectures • 19min.
- Kubernetes Configuration –> 7 lectures • 23min.
Requirements
Microservice architecture helps you to scale your product and make it more meaningful to add new features. Also your teams can be divided into smaller squads with ownership of respective domain. So its not only scaling your product but also teams around. Another important point is you will be able to easily bring new technologies with the help of message broker. We will see RabbitMQ mainly as an example but possible to pick and apply other solutions.
Here are some other benefits you can get from this course to apply your project.
* Easier to scale when high traffic hits your product, since you re removing the single point of failure from your architecture and using message broker with persistent storage feature. When your service is back, can start consuming the messages from where it left.
* Use Golang when you need and php in another, as long as you communicate with the same json structure, it won’t be problem.
* With help of Kubernetes, deployment and tracking the app health will be more robust and will reduce the down time.
* Symfony messenger bundle comes with all needed features out of the box, that will help you to start building your service without too much hassle