Ten Things I Hate About Microservices
summary
Large migration narrative with concrete fixes not fluff describes splitting a monolith using the Data Refactoring Advisor (infomap clustering), surviving a sprawl of about 10 different databases by moving to Oracle multitenant pluggable containers, standardizing on Spring Boot and CI/CD, solving distributed consistency with the microtx saga engine plus lockless reservations, replacing Kafka with Oracle Transactional event queues for transactional outbox semantics, offloading reads to Oracle True Cache, and adopting Oracle Database 23ai, ORDS, Grafana and OpenTelemetry for testing and observability.
AI-written summary · about
chapters (15)
- 0:00Microservices challenges
- 0:39Standardizing frameworks
- 1:02Data refactoring with Spring Boot
- 2:07Database per service pitfalls
- 2:51Oracle multitenant adoption
- 3:33Saga pattern for consistency
- 3:54Oracle True Cache for queries
- 4:58Kafka async challenges
- 5:43Transactional event queues
- 6:25Observability with Grafana
- 7:29Testing with Oracle 23ai
- 8:33PL/SQL via REST with ORDS
- 9:14MongoDB JSON issues
- 9:55JSON Duality Views
- 11:00Lessons learned and benefits
related talks
33mFireside chat - Monoliths, Microservices & Modernization – Practical Strategies
45mMonolith to Microservices: Modularizing Fineract 1.x
43mMicroMonolith - Top anti-patterns of distributed systems
43mGoodbye Microservices, Hello Self-Contained Systems
24mPatterns of Evolution from Monolith to Microservices
43mMigrating a Mission Critical Monolith to a #CloudNative Architecture
39m10 Tips for failing at microservices
01h 05mMigrating to Microservice Databases: From Relational Monolith to Distributed Data