Why You Should Never Build Microservices - and Why We Do It Anyway

Explore the complexities and trade-offs of microservices architecture in this conference talk. Delve into the appeal and challenges of implementing microservices, drawing from real-world experiences at Queue-it. Examine the pros and cons, discuss appropriate use cases, and consider alternatives. Learn about layered architecture, complexity management, team dynamics, deployment pipelines, and advanced network considerations. Address pitfalls such as distributed monoliths, eventual consistency, and cross-functional team requirements. Gain insights on gradual implementation, bounded contexts, and essential infrastructure for successful microservices adoption. Understand the minimum requirements, development environments, and technological considerations for building robust microservice-based systems.

Introduction
What are Microservices
Why we like Microservices
Layered architecture
Complexity
Promises
Value
People
Smaller teams
Deployment pipelines
Advanced Network layer
Multiple programming languages
Debugging
Multiple Services
Error Cases
Monitoring
Tests Debugging
Unit Tests
Pitfalls
Not enough skilled people
Distributed monolith
Eventually consistency
Crossfunctional teams
Bounded context domains
Availability reliability
Thoughts on Microservices
Perfection
Monolith
Picking out pieces
Look for bounded contexts
Layers
Architecture
Minimum requirements
Development environments
Logging monitoring
Technology