3294 views • Designing μ-services
Microservices give us the flexibility to pick the best tech stack to solve the problem optimally. But one thing that ruins the real thrill is Timeouts.
Say we have a blogging website where a user can search for blogs. The request comes to the Search service, and it finds the most relevant blogs for the query.
In the response, a field called
total_views should hold the total number of views the blog received in its lifetime. The search services should talk to the Analytics service synchronously to get the data. This synchronous dependency is the root of all evil.
The core problem: Delays can be arbitrarily large
Because the delay depending on service can be arbitrarily large, we know how long to wait for the response. We for sure cannot wait forever, and hence we introduce Timeout. Every time the Search service invokes the Analytics service, it starts a timer, and if it does not get a response in the stipulated time, it timeout and moves on.
There are 5 approaches to handling timeouts.
If you like what you read subscribe you can always subscribe to my newsletter and get the post delivered straight to your inbox. I write essays on various engineering topics and share it through my weekly newsletter.
2225 views • 114 likes • 2022-07-04
As your application evolves, supporting multiple types of clients like Desktop, Mobile apps, etc becomes tricky. The bac...
850 views • 50 likes • 2022-06-27
Running microservices in isolation does not make any sense. To get something done, multiple microservices need to talk t...
856 views • 35 likes • 2022-06-20
An engineer working on Microservices should not only just focus on engineering; there are so many other aspects to look ...
631 views • 27 likes • 2022-06-17
We all love creating microservices, but what if every team creates its own microservice uniquely and uses its own conven...
A set of courses designed to make you a better engineer and excel at your career; no-fluff, pure engineering.
Being a passionate engineer, I love to talk about a wide range of topics, but these are my personal favourites.
Arpit's Newsletter read by 17000+ engineers
🔥 Thrice a week, in your inbox, an essay about system design, distributed systems, microservices, programming languages internals, or a deep dive on some super-clever algorithm, or just a few tips on building highly scalable distributed systems.
Powered by this tech stack.