Best of Microservices — April 2026

1. 1
   Video

   The Coding Gopher·6w

   I replaced my entire stack with Postgres...

   PostgreSQL can replace a surprising number of specialized services in a typical tech stack. JSONB with GIN indexes handles NoSQL-style document storage, SELECT FOR UPDATE SKIP LOCKED turns a table into a concurrent job queue, tsvector/tsquery plus pg_trgm power full-text and fuzzy search, and the pgvector extension with HNSW indexes enables vector similarity search alongside relational data. PostGIS covers geospatial queries, declarative partitioning with BRIN indexes handles time-series workloads, materialized views replace basic data warehouse dashboards, and tools like PostgREST or pg_graphql auto-generate APIs directly from the schema. The post acknowledges limits: horizontal sharding at extreme scale and sub-millisecond in-memory caching still warrant specialized tools, but for most applications PostgreSQL alone is a cost-effective, battle-tested foundation.

   181

   10
2. 2
   Video

   The Serious CTO·6w

   11 Reliability Principles Every CTO Learns Too Late

   A pragmatic take on reliability engineering for startups, arguing that chasing high uptime targets (99.99%+) is an exponential cost trap that kills velocity before product-market fit. Key principles include: each additional nine of uptime costs 10x more in engineering overhead; resume-driven development (Kubernetes, microservices, multi-region) wastes millions solving imaginary scale problems; modular monoliths outperform premature microservices; high-availability automation itself caused AWS's 14-hour outage; boring technology is a strategic advantage since LLMs have better training data for it; error budgets replace the speed-vs-stability debate with objective data; and the maintenance ratio (50-80% of mature system costs) crushes delivery throughput. The core mindset shift: reliability is about recovery speed, not uptime percentage. A team deploying 10x/day that recovers in 5 minutes beats a complex self-healing system nobody understands. Exceptions exist for fintech, healthcare, and telecom where reliability is the product itself.

   124

   3
3. 3
   Article

   InfoWorld·7w

   Multi-agent is the new microservices

   Multi-agent AI systems are being over-adopted in the same way microservices were — applied broadly before teams have problems that actually warrant the complexity. Anthropic, OpenAI, Microsoft, and Google all advise starting with the simplest solution: a single optimized LLM call, then retrieval, then tools, then a single agent loop. Only add a second agent when you can clearly identify parallelizable tasks, context pollution, or specialization needs. Multi-agent architectures cost significantly more in tokens, observability, error handling, and maintenance. Most enterprise teams don't yet have problems worth decomposing across agents, and adding agents won't fix weak retrieval, vague tools, or poor documentation — it will amplify those problems.

   114

   3
4. 4
   Article

   System Design Codex·7w

   What is the BFF Pattern?

   The Backends-for-Frontends (BFF) pattern involves creating dedicated API gateways for each client type (web, mobile, partner APIs). Each BFF acts as a specialized intermediary that handles client-specific concerns like rate limiting, authentication, caching, and header sanitization. Key advantages include improved resiliency through isolation, client-specific optimization, and faster development velocity. Drawbacks include potential code duplication, growing complexity, and BFF proliferation. Best practices recommend clearly defining client requirements, extracting shared logic into libraries, maintaining clear boundaries, and monitoring performance.

   63

   2
5. 5
   Article

   ByteByteGo·6w

   EP210: Monolithic vs Microservices vs Serverless

   A curated system design newsletter covering five topics: a comparison of monolithic, microservices, and serverless architectures with practical tradeoffs; CLI vs MCP for AI agents across six dimensions including token cost, auth, and governance; a comparison of five major coding agents in 2026; an overview of essential AWS services and where they fit in production stacks; and a beginner-friendly visual explanation of JWT structure and security.

   49

   1
6. 6
   Article

   monday Engineering·5w

   Building a Reliable and Extendable Notifications Platform

   monday.com's engineering team shares how they rebuilt their notifications platform from a Ruby on Rails monolith into a scalable TypeScript microservice. The new system uses a three-stage SQS-based orchestration pipeline (processing, filtering, delivery) with exponential backoff, per-channel retry logic, and DLQ support. A JSON-based app feature format and SDK allow developers to add new notification types in about an hour. The platform now handles over 8 million notifications daily across email, mobile, Slack, MS Teams, and in-app channels, with Datadog instrumentation for observability.

   37

   1
7. 7
   Article

   monday Engineering·4w

   Creating Contractual Service Communication

   monday.com engineering team describes how they replaced implicit, 'stringly typed' service contracts with explicit, versioned JSON Schemas across their microservices architecture. Starting with their Reporter Service (handling ~100M daily events), they inferred initial schemas from production payloads using LLMs, iterated until achieving 100% validation rates, and centralized schemas in a Git repository. They auto-generated TypeScript interfaces and Go structs from schemas, wired compatibility checks into CI to catch breaking changes before deployment, and assigned clear ownership per schema. The result was an internal event catalogue, reduced schema-drift incidents, and a foundation for exposing internal event streams as stable public APIs.

   83

   2
8. 8
   Article

   Istio·6w

   Announcing Istio 1.28.6

   Istio 1.28.6 is a patch release focused on security fixes and bug corrections. Key additions include Helm v4 server-side apply support, authorized namespace configuration for debug endpoints, and CIDR blocking for JWKS URIs during JWT validation. Notable fixes address a webhook failurePolicy field ownership conflict during helm upgrade, serviceAccount regex matching in AuthorizationPolicy, Gateway API CORS origin parsing, istiod crash with ambient mode and multi-network configs, a retryBudget default percent bug (0.2% instead of 20%), missing size limits on gzip-decompressed WASM binaries, and a race condition causing h2 ping errors.

   27
9. 9
   Article

   freeCodeCamp·5w

   How I Built a Production-Ready CI/CD Pipeline for a Monorepo-Based Microservices System with Jenkins, Docker Compose, and Traefik

   A comprehensive guide to building a production-ready CI/CD pipeline for a monorepo-based microservices system on a single Linux server. Covers running Jenkins in Docker, using Traefik as a reverse proxy with auto-renewing Let's Encrypt HTTPS certificates, and writing a Jenkinsfile that detects which microservices changed per commit and redeploys only those affected services. Includes full Docker Compose configurations, step-by-step Jenkins setup, GitHub webhook integration, a detailed troubleshooting section covering real production errors (dubious ownership, SSH vs HTTPS auth, missing Compose plugin, timezone issues, pnpm timeouts), and a host-vs-container mental model reference table.

   18

   2
10. 10
    Article

    ByteByteGo·5w

    How DoorDash Launches a New Country in One Week

    DoorDash rebuilt its Dasher onboarding system using a three-layer modular architecture: a thin orchestrator for routing, composable workflow definitions per market, and self-contained step modules behind standardized interfaces. This replaced a legacy system of hard-coded country-specific if/else branches and fragmented state across multiple database tables. The new design uses a single JSON status map for all onboarding state, enabling atomic per-step updates and simple progress reconstruction. The result: Puerto Rico launched in one week, Canada in two weeks, Australia in under a month, and New Zealand with almost no new code. The post covers the architectural layers, the status map design, the parallel migration strategy, and honest tradeoffs including coordination overhead and the limits of module reuse across fundamentally different regulatory regimes.

    17

    5