// Topics / Microservices

Microservices

    Testing Microservices Without Losing Your Mind Microservices fail at the seams. A layered test strategy that keeps feedback fast and catches integration issues before production. testing microservices go Distributed Systems Patterns I Keep Reaching For The patterns that actually survive production across failure handling, consistency, messaging, coordination, and scaling. distributed-systems architecture microservices GraphQL Federation: I'm Still Skeptical A year after my GraphQL post, federation is the new hotness. I still think most teams don't need it. api microservices opinion API Gateway Patterns That Actually Work Edge gateways, BFFs, and service mesh ingress -- what I've learned running them at Decloud and at large telecoms. api microservices architecture gRPC Patterns That Actually Work in Production Hard-won gRPC patterns from building Decloud's service mesh. Proto design, Go implementation, error handling, and the mistakes that cost us weekends. api go microservices Your Monolith Is Probably Fine Most teams shouldn't be migrating to microservices. Here's how to tell if you actually should, and how to do it without wrecking your delivery for eighteen months. microservices architecture go Istio: Powerful, Painful, and Probably More Than You Need My honest take on evaluating Istio at the fintech startup — what it actually gives you, what it costs you, and why most teams should think twice before adopting it. kubernetes microservices infrastructure Securing Microservices: What Actually Works You split the monolith. Now every service-to-service call is an attack surface. How I think about identity, authorization, encryption, and secrets management. security microservices architecture Service Mesh: You Probably Don't Need One I evaluated Istio and Linkerd for our microservices at the fintech startup. My conclusion: most teams are buying complexity they haven't earned yet. kubernetes microservices Why We Went Event-Driven (and What Nearly Broke) Lessons from building event-driven systems at the fintech startup and a mobility startup -- what worked, what broke, and why I'd do it again. architecture microservices Why Microservices Aren't Always the Answer Most teams adopt microservices too early and pay for complexity they don't need yet. A well-structured monolith is faster, simpler, and keeps your options open. architecture microservices startups