Distributed Systems
Six best practices for backend design in distributed system
Most modern software systems are distributed systems, but designing a distributed system isn’t easy. Here are six best practices to get you started.
Distributed Systems
Explore strategies for building, debugging, and operating complex distributed systems. Deep dives into observability, resiliency, and end-to-end visibility across services.
Distributed Systems
How to recover your architecture after drift and erosion
To effectively guide the evolution of a software system and ensure its long-term stability and maintainability, it’s crucial to understand the phenomena of architectural drift and erosion.
Distributed Systems
Strategies for managing architectural technical debt that DON’T work
The most significant relief from performance issues and costly technical liabilities comes from resolving architectural technical debt. This blog post explores best strategies to achieve that.
Distributed Systems
Understanding architectural technical debt
While most resources and tools today focus on code-level technical debt, it is Architectural Technical Debt (ATD) that incurs the highest "interest rates" and imposes the most significant constraints on the evolution of a software system.
![[Part 6] Six modern software architecture styles: P2P](https://www.multiplayer.app/blog/content/images/size/w600/2025/11/Six-modern-software-architecture-styles-4.png)
Distributed Systems
[Part 6] Six modern software architecture styles: P2P
Sixth instalment in the "Six modern software architecture styles" blog post series. In short: Liberté, Égalité, Fraternité for all the peers!
![[Part 5] Six modern software architecture styles: Edge computing](https://www.multiplayer.app/blog/content/images/size/w600/2025/11/Six-modern-software-architecture-styles-3.png)
Distributed Systems
[Part 5] Six modern software architecture styles: Edge computing
Fifth instalment in the "Six modern software architecture styles" blog post series. In short: Bring computation and data storage closer to the end user.
![[Part 4] Six modern software architecture styles: Serverless](https://www.multiplayer.app/blog/content/images/size/w600/2025/11/Six-modern-software-architecture-styles-2.png)
Distributed Systems
[Part 4] Six modern software architecture styles: Serverless
Fourth instalment in the "Six modern software architecture styles" blog post series. In short: Build and run services without having to manage the underlying infrastructure.
![[Part 3] Six modern software architecture styles: Event-Driven](https://www.multiplayer.app/blog/content/images/size/w600/2025/11/Six-modern-software-architecture-styles-1.png)
Distributed Systems
[Part 3] Six modern software architecture styles: Event-Driven
Third instalment in the "Six modern software architecture styles" blog post series. In short: Your components or services communicate through events.
![[Part 2] Six modern software architecture styles: Microservices](https://www.multiplayer.app/blog/content/images/size/w600/2025/11/Six-modern-software-architecture-styles.png)
Distributed Systems
[Part 2] Six modern software architecture styles: Microservices
Second instalment in the "Six modern software architecture styles" blog post series. In short: partition your problem into multiple, independent chunks that are scaled independently.
![[Part 1] Six modern software architecture styles: Monolithic](https://www.multiplayer.app/blog/content/images/size/w600/2025/11/monolithic.png)
Distributed Systems
[Part 1] Six modern software architecture styles: Monolithic
Leveraging tried-and-tested solutions saves time, ensures reliability, and helps avoid common pitfalls. We look at six common architectural styles used in distributed systems and talk about how to choose the best one for your use case.