Autonomous microservices don't share data. Period - Dennis van der Stelt
Did you start out building microservices, and somehow ended up with a distributed monolith? If a small change in business logic or in data requires you to modify code in more than one service, you probably did. Isn't it unbelievable that even using the latest technologies like Docker, Service Mesh, Serverless, and more, doesn't help? I will tell a story in which we'll take a different look at microservices and discuss why technology doesn't change coupling or autonomy at all. How we need to take a step back and stop sharing data between services. NDC Conferences https://www.ndcconferences.com https://ndccopenhagen.com

▶︎
Lessons learned form Kafka in production (Tim Berglund, Confluent)

▶︎
Finding your service boundaries - a practical guide - Adam Ralph

▶︎
Microservices and Rules Engines – a blast from the past - Udi Dahan

▶︎
Microservices • Martin Fowler • GOTO 2014

▶︎
Avoiding Microservice Megadisasters - Jimmy Bogard

▶︎
Embracing Messaging and Eventual Consistency in your Microservices Solutions - Michele Bustamante

▶︎
Six Little Lines of Fail - Jimmy Bogard

▶︎
Martin Fowler – Microservices

▶︎
The Many Meanings of Event-Driven Architecture • Martin Fowler • GOTO 2017

▶︎
Trump Attends NBA Finals, Cries Election Fraud in California & Storms Out of Interview

▶︎
Principles Of Microservices by Sam Newman

▶︎
Managing Data in Microservices

▶︎
System Design Explained: APIs, Databases, Caching, CDNs, Load Balancing & Production Infra

▶︎
Udi Dahan - If (domain logic) then CQRS, or Saga?

▶︎
Not Just Events: Developing Asynchronous Microservices • Chris Richardson • GOTO 2019

▶︎
Migrating to Microservice Databases: From Relational Monolith to Distributed Data - Edson Yanaga

▶︎
Using sagas to maintain data consistency in a microservice architecture by Chris Richardson

▶︎
Data Consistency in Microservices Architecture (Grygoriy Gonchar)

▶︎
System Design Course – APIs, Databases, Caching, CDNs, Load Balancing & Production Infra

▶︎
