Why You Need a Platform for Interservice Interaction
summary
A talk about designing a platform for inter-service communication in microservice architectures, covering what such a platform is, why teams need it, and practical steps to build one quickly. It targets teams migrating from a monolith or starting with services and focuses on the platform-level technologies and approaches for service-to-service interaction.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:06Monolith problems and service shift
- 3:16Service growth and inconsistency
- 6:03Swagger and schema issues
- 9:36Developer goals in service interaction
- 11:18Need for interaction platform
- 13:25Protocol and framework selection
- 16:38gRPC load balancing issues
- 20:06gRPC problems and alternatives
- 22:57Platform simplicity and minimalism
- 25:48Twitch solution and benefits
- 27:55Final platform architecture
- 30:04Prototyping and code generation
- 33:14Code generation results and benefits
- 35:45Request metadata and observability
- 37:12Protocol Buffers and simplicity
- 39:18Platform benefits summary
- 40:01Q&A
related talks
54mMicroservice architecture: approaches and technologies
32mThe right questions to ask when using microservices
49mTeam topologies and the microservice architecture
38mIntroduction to Microservices
38mFrom Monolith to Microservices
31mWhat lies beyond microservice architecture? From Microservices to Distributed Platform Architecture
23mBuilding an IT Platform for Investment Business
49mMicroservices: An unexpected Journey