3min chapter

DevOps Paradox cover image

DOP 216: Simplify Microservice Development With Signadot

DevOps Paradox

CHAPTER

The Anti-Pattern of Tight Coupling

We have the issue of how we architect applications because I still see, even though I hope that I wouldn't, very often that companies develop software in a way that 57 different applications need to be deployed and developed at the same time for a single change to work. We rely on or rather this model relies on the services being able to propagate that context all through. This is typically done using open telemetry or equivalent libraries that make it very, very simple to do it. The concept of context propagation is also used in tracing, right, in the sort of distributed tracing world that is anyway useful to have when you have microservices based applications.

00:00

Get the Snipd
podcast app

Unlock the knowledge in podcasts with the podcast player of the future.
App store bannerPlay store banner

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode

Save any
moment

Hear something you like? Tap your headphones to save it with AI-generated key takeaways

Share
& Export

Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more

AI-powered
podcast player

Listen to all your favourite podcasts with AI-powered features

Discover
highlights

Listen to the best highlights from the podcasts you love and dive into the full episode