Queus vs Pub/Sub

As the journey of learning about microservice continues, there is a concept of async collaboration between services.

Why is that important? Async communication allows for long running process to not block the client. It allows for snappier, better user experience since we will update the client/UI immediately, and return the calculated answer later.

E.g. sending the client an email. The user signs up, and as a part of the process we send the user an email. There shouldn’t be any reason for the user to wait until that email has been sent. So we immediately redirect him to the homepage while generating a job of “sending an email”.

YWS

The Goal: creating a local “aws-ish” so i can play with these tools locally before “commiting” to the tools in the cloud which costs money.

Why? This will help me learn about these subjects, implementing and creating is the best way to learn. also very fun :)

This is a ongoing summary of the book “Building Microservices” by Sam Neuman.

Chapter 1 - What are microservices

From the book:

Microservices are small, autonomous services that work together.

Breaking it down we get:

• Small - in terms of code base and team.
• Autonomous - separate entities, deployed as a independent service.

Communication between services are through network calls.

Thoughts are made about what is exposed vs hidden.

Key Benefits

Technology Heterogeneity

Since each service is independent, we can choose the right tools for the job, for example: