Microservices Design Patterns, Hugh McKee at Scalac's Event

The talk was given on Between Business & Tech. Episode 1: The Microservices online event.

Microservices Design Patterns

There are many ways to design patterns for building microservices, and most of them are wrong. Actually, that is not true. The fundamental objectives for implementing microservice systems are speed and agility. Speed, of course, is how quickly you can get things done. Regardless of what design patterns you use, if you can quickly build, fix, enhance, and rapidly evolve your microservices, you are heading in the right direction. Agility is the flexibility to move rapidly across the entire development lifecycle while living happily in production.

But we can always do better. Right?

That is what this talk is about. We will take a look at some of the more common microservice design patterns. And we will compare them to some of the alternatives. For example, what is the more common microlith design pattern, and how getting serious about loose coupling guides the evolution to ways that increase your speed and agility? We will also look at why it is micro at the code level and the data level. Finally, we will cover some practical guidelines, such as why your microservices should do the least amount of work while your users are waiting and techniques for doing that.

Hugh McKee, Lightbend
Hugh McKee is a developer advocate at Lightbend. He has had a long career building applications that evolved slowly, inefficiently utilized their infrastructure, and were brittle and prone to failure. Hugh has learned from his past mistakes, battle scars, and a few wins. And the learning never stops. Now his focus is on helping other developers and architects build resilient, scalable, leading-edge systems. Hugh frequently speaks at conferences around the world. He is the author of Designing Reactive Systems: The Role Of Actors In Distributed Architecture.