Eberhard Wolff

Microservices? Monoliths? An Annoying Discussion!

Stop debating microservices vs. monoliths. Without proper modularization, both architectures are doomed to fail.

Microservices? Monoliths? An Annoying Discussion!
#1about 3 minutes

The flawed debate between monoliths and microservices

The common narrative pitting simple monoliths against complex microservices ignores the significant deployment and testing challenges of large monolithic systems.

#2about 3 minutes

Why complex microservice architectures like Netflix succeed

The success of complex systems like Netflix's architecture is not due to its complexity, but to effective modularization and information hiding.

#3about 5 minutes

The real problem is poor modularization, not architecture choice

Whether you have a thousand microservices or a class with a thousand methods, the root issue is a failure to create loosely coupled modules.

#4about 8 minutes

How to design modules around business functionality

Apply principles like information hiding and bounded contexts to build modules around business capabilities, not shared data models.

#5about 3 minutes

Aligning architecture with organizational goals and trust

To realize the productivity gains of microservices, organizational structures must trust teams with autonomy over deployment and technology choices.

#6about 2 minutes

Conclusion: Focus on fundamentals beyond the hype

The debate over monoliths versus microservices is a distraction from the fundamental principles of good modularization and organizational design.

Related jobs
Jobs that call for the skills explored in this talk.

Featured Partners

From learning to earning

Jobs that call for the skills explored in this talk.

Rust and GoLang

Rust and GoLang

NHe4a GmbH
Karlsruhe, Germany

Remote
55-65K
Intermediate
Senior
Go
Rust