Distributed Computing Musings

Modern microservices have various integration points in form of external APIs, databases etc.

In any software application we generally require talking to multiple microservices to achieve a single business outcome.

Once you start dealing with cloud systems, you need to grapple with the reality that failure is a question of when & not if.

In the last post, we saw how deep-checks & health-checks can prevent your application from failing due to a bad deployment.

Understanding the problem In a cloud-native environment where your application is powered by multiple services with a complex dependency graph, a single developer shipping a bug in one of the services can turn into a cascading failure post deployment.

Couple of years back I wrote a post describing the thundering herd problem.

What are we solving?

API gateways are probably one of the first few keywords you hear when you enter the world of cloud computing.

Continuing from our previous cloud bits post about service configuration, we will explore the topic of service discovery in this post.

Today most of the application software we develop ends up getting deployed to the cloud & along with it comes its own set of challenges.