Vincent Marquez Interview
summary
Work centers on designing safe APIs and choosing back pressure trade-offs versus fully asynchronous behavior, with no one-size answer and decisions driven by service guarantees. Microservices cause recurring pain around service discovery and versioning as deployments and incompatible APIs proliferate. Adopting functional programming shifts failures from correctness to performance — roughly 99.9% performance-related issues — so effort focuses on scaling, latency, and deployment compatibility rather than nulls or exceptions.
AI-written summary · about
related talks
38mMicroservices, a bittersweet symphony
45mMicroservices: A retrospective
16mMicroservice Challenges
50mEmbracing Microservices
52mMovin beyond request-reply: how smart APIs are different
54mThe Long Sad History of Microservices
59mEffective Microservice Communication and Conversation Patterns
23mWhy You Had a Bad Time With Microservices