Skip to content
0:00 / 0:00

#distributedmonolith#microservices#softwarearchitecture

Don’t Build a Distributed Monolith - Jonathan "J." Tower - NDC London 2023

NDC Conferences

230K subscribers • 110 videos on Hallway • Conference channel

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Jonathan Tower, software architect and consultant
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

224K views3 years ago2 recommendations

Software designDistributed systemsSoftware architectureMicroservices and monolithsScaling and large-scale architecture

Jonathan Tower explains how to avoid common mistakes in microservices implementations that lead to building a tightly coupled distributed monolith.

Don’t Build a Distributed Monolith: How to Avoid Doing Microservices Completely Wrong - Jonathan "J." Tower As a consultant, I get to see many systems built by many different developers. Recently, I’ve seen an uptick in the number of systems built with a microservice architecture in mind, but those systems often include a lot of the same mistakes that keep them from working well. In this session you’ll learn from my experiences and get pointers on what to avoid in your microservices implementations so that you don’t accidentally build something which has all the worst aspects of a monolithic application and the worst aspects of microservices These monsters are what I call “distributed monoliths”, and I can help you avoid building one accidentally. Check out our new channel: NDC Clips: @ndcclips Check out more of our featured speakers and talks at ndcconferences.com/ ndclondon.com/

Why it's here

2 people recommend this

What people say. Recommended as a helpful guide on when and why to avoid microservices and distributed monoliths.

u/Wide-Answer-2789in r/softwarearchitecture • Recommends

On “Looking for thoughts about an architectural problem”

Yes, that is valid question To answer that to yourself you need a little bit more theory I would suggest start from : link to this video link to this video Serverlessland.com

u/Revision2000in r/softwarearchitecture • Recommends

On “How to start learning microservices in a structured way?”

There’s plenty of good materials posted already for you to get started. That answers the implementation. I’d just like to point out these videos as to when and why you should (not) use microservices.  * Don’t build a distributed monolith  * Why are software engineers quitting microservices  TL;DR microservices often solve organizational challenges, at the cost of increased complexity. So as always “it depends”.