Best of Microservices — March 2026

  1. 1
    Article
    Avatar of wundergraphWunderGraph·6w

    Design Like a Monolith, Implement as Microservices

    The monolith vs. microservices debate is framed as a false dichotomy. The real insight is that API design and API implementation are separate concerns that should be handled differently: design top-down as a unified whole (monolith thinking), implement distributed across teams (microservices thinking). Traditional GraphQL Federation merges these concerns, letting each team design and implement their slice, which leads to API fragmentation. WunderGraph's Fission and Hub tools aim to separate these layers — a design phase where the supergraph is treated as a single coherent schema, and an implementation phase where teams independently build their assigned subgraphs. Three trends driving this approach: organizations scaling past coordination thresholds, AI agents needing coherent APIs, and platform engineering demanding golden paths.

  2. 2
    Video
    Avatar of youtubeYouTube·8w

    Should you learn Go in 2026?

    A Go developer and former Twitch senior engineer makes the case for learning Go in 2026 despite AI disruption and tech layoffs. Key arguments include Go's dominance in cloud-native tooling (Kubernetes, Docker), its suitability for microservices, its simplicity making it AI-friendly for code generation, its robust standard library, and strong job market demand with competitive salaries. The GitHub 2025 developer survey is cited showing Go among the most admired and desired languages.

  3. 3
    Video
    Avatar of davidbombalDavid Bombal·5w

    Vibe coding is scary real!

    A Cisco executive shares how vibe coding transformed a 15-year-old, 500,000-line proprietary 5G network function into a modern Golang microservices architecture using gRPC in just one week — a project that would have taken over a year traditionally. The code was reduced to 106,000 lines and passed initial smoke tests. The exec went from skeptic to believer, predicting AI-assisted coding will become the default way software is developed within 6–12 months, while acknowledging extensive validation is still required before production release.

  4. 4
    Article
    Avatar of microservicesioMicroservices.io·5w

    Microservices Platforms - part 6: Build platform

    Part 6 of a series on Microservices Platforms, this installment covers the Build platform — the component responsible for providing deployment pipeline infrastructure, reusable pipeline components, and pipeline templates. The Build platform, alongside the Deployment platform, defines the path changes take from a developer's laptop to production, enabling service teams to focus on business value rather than pipeline management. Full content is behind a paywall.

  5. 5
    Article
    Avatar of baeldungBaeldung·4w

    Distributed Transaction Management Using Apache Seata

    Apache Seata is an open source distributed transaction manager originally from Alibaba, now part of the Apache Incubator. It solves the problem of maintaining atomicity across multiple microservices that each have their own database. The setup involves running a Seata Server as a transaction coordinator (via Docker), adding the seata-spring-boot-starter dependency, configuring seata.conf and application.properties, and creating an undo_log table for AT mode. The @GlobalTransactional annotation marks the start of a distributed transaction. For Spring Boot, XID propagation between services requires a custom ClientHttpRequestInterceptor for outbound calls and a servlet filter for inbound calls. Spring Cloud simplifies this by handling most propagation automatically, though RestClient and WebClient still need manual configuration.

See all Microservices archives