Skip to content
Hallway
0:00 / 0:00

#distributedmonolith#microservices#softwarearchitecture

Don’t Build a Distributed Monolith: How to Avoid Doing Microservices Wrong - Jonathan J. Tower

NDC Conferences

230K subscribers • 110 videos on Hallway • Conference channel

YouTube
  • Recommended by 1 person: 1 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.

11K views2 years ago1 recommendation

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 This talk was recorded at NDC Porto in Porto, Portugal. #ndcporto #ndcconferences #architecture #cloud #softwaredeveloper Attend the next NDC conference near you: ndcconferences.com ndcporto.com/ Subscribe to our YouTube channel and learn every day: /@NDC Follow us on our Social Media: facebook.com/ndcconferences twitter.com/NDC_Conferences instagram.com/ndc_conferences/ 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.

Why it's here

1 person recommends this

What people say. Recommended as a great talk on the trade-offs of monoliths versus microservices.

u/Revision2000in r/softwarearchitecture • Recommends

On “Emerging from burnout. Are there new web architecture paradigms in the past few years?”

Not specific to web, but rather to how applications can be architected in general: maybe Vertical Slice Architecture along with modular monolith.  Here’s some videos that sort of tie in to these:  * [Don’t Build a Distributed Monolith: How to Avoid Doing Microservices Completely Wrong - Jonathan "J." Tower]  * Model Mitosis: Stop making the wrong choice between microservices and monolith
25View on Reddit

u/Revision2000in r/softwarearchitecture • Recommends

On “Monolith vs. Modular: Structuring Our Internal Tools”

Thanks!  I’m in the Java space, where I’ll usually structure my projects with Maven modules or Java packages - perhaps through Spring Modulith.  I’m not that familiar with Rust, but I think I’ll take a look at this “tangle guard” - at times it can be interesting to see what solutions are used by other languages 🙂 As for the monolith versus microservices topic, I found this talk quite good: [Don’t Build a Distributed Monolith: How to Avoid Doing Microservices Completely Wrong] (YouTube)
2View on Reddit