---
title: "Discussion on \"Invisible Coupling: When Your Microservices Become a Distributed Monolith\" | Hashnode"
description: "Discussion on \"Invisible Coupling: When Your Microservices Become a Distributed Monolith\". Synchronous call chains turn microservices into a distributed monolith. How temporal coupling costs you p99 latency, money and resilience."
url: "https://hashnode.com/posts/invisible-coupling-distributed-monolith/6ae0928b630ccbf172cdc0fc"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Invisible Coupling: When Your Microservices Become a Distributed Monolith](https://willpeixoto.dev/invisible-coupling-distributed-monolith?utm_source=hashnode&utm_medium=feed)

Synchronous call chains turn microservices into a distributed monolith. How temporal coupling costs you p99 latency, money and resilience.

Oct 27 · 13 min read · willpeixoto.dev  
Updated Oct 30  
Read the article

-   [#microservices](https://hashnode.com/tag/microservices)
-   [#software-architecture](https://hashnode.com/tag/software-architecture)
-   [#event-driven-architecture](https://hashnode.com/tag/event-driven-architecture)
-   [#serverless](https://hashnode.com/tag/serverless)
-   [#aws](https://hashnode.com/tag/aws)

## Written by

[Will Peixoto](https://hashnode.com/@willpeixoto)

@willpeixoto · São Paulo, Brasil

  
[View profile](https://hashnode.com/@willpeixoto)

Staff Engineer at Serverless Guru · AWS Community Builder · AWS User Group São Paulo

Staff Engineer at Serverless Guru, AWS Community Builder and one of the leaders of AWS User Group São Paulo. Writing about serverless, event-driven architecture and AI agents on AWS, with code and the trade-offs on the table.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
