-
Understanding everything about microservices is hard, and we all made the same mistakes when we started. That's why I started this repository to share 👉 Why Sync Req/Res should be avoided 👉 Why Pub/Sub makes your system more reliable github.com/aleixmorgadas/reactive-microservices-workshopPermalink On twitter.com
♻️ 1 Retweets ❤️ 8 Favorites Mood +1 🙂
-
I aim to create a project to help people make workshops within their organizations about Event-Driven Architecture and Resilient Microservices. Named as Reactive Microservices because @kanekotic used it in a super cool presentation he did 😄Permalink On twitter.com
-
The workshop will have a simple model. Posts -> Comments Instead of focusing on the model itself, I will focus on Architecture and why some patterns are less resilient than others.Permalink On twitter.com
-
The idea is to create a workshop that kinda follows the natural evolution when you start with Microservices You start with two services, two databases, and then one talking to the other Commonly, you don't find any problem when you don't have any traffic It just works fine...Permalink On twitter.com
-
for some time. When you start having some problems, you might start with some Monitoring tools. Here, I will preconfigure all the tooling so you can focus on understanding why things happen instead of monitoring tooling configurationPermalink On twitter.com
-
Yet, we need to emulate some problematics that's when Comments Service comes into play. It will have a way to emulate problems like 👉 Timeouts 👉 Slow responses 👉 Transactionality problemsPermalink On twitter.com
-
That emulation will help us to see how patterns like 👉 Circuit Breaker 👉 RateLimiter 👉 Retry And their limits. Experimenting with the patterns meanwhile visualizing the behavior on the monitoring system.On twitter.com
-
Then, we will play with bad scenarios. 👉 What happens if Comments System is down? 👉 Data lost? 👉 Data consistency?Permalink On twitter.com
-
Introducing Kafka Moving to Request/Response to Pub/Sub Messaging. Here we will see the benefits of Message/Event-Driven Architecture. We will reply the same issues we had and see how the EDA helped usPermalink On twitter.com
-
Then, we will introduce zipkin as distributed tracing system. I think it's important to know more tooling that can give you insights about why things happen the way they happen, and how to debug distributed systems. zipkin.io/Permalink On twitter.com
-
The tools I use for this workshop are: 👉 @micronautfw 👉 @Docker 👉 @grafana 👉 @PrometheusIO 👉 @zipkinproject 👉 @apachekafkaPermalink On twitter.com
-
Did you miss anything you would like to see in this workshop? 🤔Permalink On twitter.com
-
Maybe service discovery with Consul? consul.io/Permalink On twitter.com
-
The amount of stuff I need to start in order to do a workshop about Reactive Microservices is absurd. And I think I still miss Grafana Loki for logs and Consul 🤦 How the hell a person starting in this profession can even handle all this cognitive load?Permalink On twitter.com
-
An screenshot of Comments Service 😄Permalink On twitter.com
-
Here an example of how to configure Comments Service to behave to experiment with it 👏Permalink On twitter.com