Best of Microservices — February 2026

1. 1
   Article

   freeCodeCamp·8w

   Master Kubernetes Through Production-Ready Practice

   A 6-hour hands-on Kubernetes course posted on freeCodeCamp's YouTube channel, developed by Saiyam Pathak. It covers deploying a cloud-native microservices stack from scratch, including Kubernetes architecture (Control Plane, Worker Nodes, CRI/CNI/CSI), Gateway API for traffic management, CloudNativePG for PostgreSQL, cert-manager for HTTPS, and full-stack observability with Prometheus and Grafana. The course targets production-grade deployments rather than isolated command memorization.

   201

   6
2. 2
   Article

   ITNEXT·10w

   Sandwich Architecture

   The 'Sandwich Architecture' is a system topology that sits between layered and service-based architectures. It consists of a shared integration layer on top, domain-level services in the middle, and a shared data layer at the bottom. This pattern emerges naturally when a layered system's domain layer is split into subdomains while the integration and data layers remain intact. It suits medium-sized projects with complex domain logic, offering a pragmatic balance of simplicity and flexibility. The article covers its structure, performance characteristics, dependency options (orchestration, data change notifications, choreography), applicability, and evolution paths. Real-world examples include Blackboard Systems, Space-Based Architecture, Service-Based Architecture, and CQRS.

   137

   2
3. 3
   Video

   ForrestKnight·12w

   I Can't Believe Rust is Replacing Java

   XAI completely rewrote X's recommendation algorithm, replacing dozens of Java/Scala microservices with four Rust components and a Grok-based transformer. The old system used hand-engineered features and explicit weights across interconnected services, while the new architecture moves intelligence into an ML model with Rust handling orchestration. The shift addresses JVM garbage collection issues for sub-millisecond latency requirements and reflects a broader industry trend of using Rust for performance-critical infrastructure alongside AI-driven systems.

   93

   25
4. 4
   Article

   ByteByteGo·9w

   How Uber Reinvented Access Control for Microservices

   Uber built Charter, an attribute-based access control (ABAC) system to handle authorization across thousands of microservices at microsecond latency. Traditional role-based policies couldn't express complex conditions like region-matching or ownership relationships. Charter distributes policies to services, which evaluate them locally using an embedded authfx library. Conditions are written in Google's Common Expression Language (CEL) and evaluated against attributes fetched at runtime from typed attribute stores (actor, resource, action, environment). A real-world example shows how a single ABAC policy replaced thousands of individual Kafka topic policies by dynamically checking ownership data from Uber's uOwn service. Since adoption, 70 Uber services use attribute-based policies, gaining fine-grained, dynamic, and scalable authorization without code deployments.

   80

   2
5. 5
   Article

   ITNEXT·10w

   I follow an architecture principle I call The Law of Collective Amnesia

   Software systems inevitably drift from their original design as teams change and new requirements emerge. To combat this "collective amnesia," design systems where the correct architectural path is the easiest one to follow. Use contracts as constraints, control entry/exit points, build modular interfaces from day one, and assume future developers won't understand or follow your intentions. Documentation alone won't prevent architectural decay—structural guardrails that make the right choice the path of least resistance will.

   78

   8
6. 6
   Article

   System Design Codex·10w

   Airbnb's Move from Monolith

   Airbnb migrated from a Ruby on Rails monolith ("monorail") to a Service-Oriented Architecture with four layers: data services, derived services, middle-tier services, and presentation services. The migration used dual reads with response comparison for read paths and shadow databases for write paths to ensure correctness before switching traffic. Key principles included single service data ownership, specific concerns per service, event-driven data changes, and proper observability. Important lessons emphasized investing in migration infrastructure early, simplifying dependencies, recognizing cultural organizational change, and viewing migration as an ongoing journey.

   75

   8
7. 7
   Article

   ByteByteGo·11w

   How LinkedIn Built a Next-Gen Service Discovery for 1000s of Services

   LinkedIn replaced its decade-old Zookeeper-based service discovery system with a next-generation architecture using Kafka for writes and gRPC/xDS for reads. The new system handles hundreds of thousands of service instances with 10x better median latency (P50 < 1s vs 10s) and 6x better P99 latency. Key improvements include horizontal scalability through Go-based Observer components, eventual consistency over strong consistency, multi-language support via xDS protocol, and cross-fabric capabilities. The migration used a dual-mode strategy where applications ran both systems simultaneously, with automated dependency analysis to safely transition thousands of services without downtime.

   72
8. 8
   Article

   InfoQ·9w

   Reducing Onboarding From 48 Hours to 4: Inside Amazon Key’s Event-Driven Platform

   Amazon Key's engineering team overhauled its event platform from a tightly coupled monolithic architecture to a centralized event-driven system built on Amazon EventBridge. The redesign uses a single bus, multi-account pattern where a core EventBridge bus routes domain events to isolated subscriber accounts. A centralized schema repository with a custom client library enforces consistent data contracts across producers and consumers. Infrastructure provisioning is automated via reusable AWS CDK constructs. The results: ~2,000 events/second processed at p90 latency of ~80ms, 99.99% success rate, service onboarding reduced from 48 hours to 4, and integration time cut from ~40 hours to ~8.

   54
9. 9
   Article

   Spring·9w

   Spring Boot 4.0.3 available now

   Spring Boot 4.0.3 has been released. This is a maintenance release in the 4.0.x line, available now from the Spring project at Broadcom.

   44
10. 10
    Article

    monday Engineering·11w

    From API Chaos to Collaborative Graph

    Monday.com's engineering team solved API chaos at scale by implementing Federated GraphQL as a centralized API engine. The solution replaces fragmented REST endpoints with a unified supergraph, eliminating boilerplate for versioning, limits, documentation, and authorization. Producers focus only on business logic while consumers get a single endpoint with dynamic field selection, consistent standards, and automatic type generation. The architecture includes CI/CD schema publishing, API wrappers for common functionality, and a central router for observability and rate limiting.

    37
11. 11
    Article

    iO tech_hub·11w

    Next.js at Enterprise Level

    Scaling Next.js to enterprise level requires moving beyond default configurations. Start with high-ROI wins like CDN implementation and vertical scaling, then progress to horizontal scaling with shared Redis caching to avoid cold cache problems across replicas. Implement API gateways for centralized authentication, use blob storage with signed URLs for file uploads, and adopt event-driven architecture for high-volume interactions. Optimize with HTTP/2 and gRPC for internal communication. Define SLAs/SLOs upfront, measure with monitoring and load testing, and iterate based on bottlenecks rather than adopting everything at once.

    36
12. 12
    Article

    Spring·9w

    Spring Boot 3.5.11 available now

    Spring Boot 3.5.11 has been released. This is a maintenance release in the 3.5.x line, available now from the Spring project under Broadcom.

    18
13. 13
    Article

    freeCodeCamp·10w

    How to Build Your Own Circuit Breaker in Spring Boot – and Really Understand Resilience4j

    Learn how circuit breakers work by building one from scratch in Spring Boot. The tutorial walks through implementing a thread-safe state machine with explicit failure tracking, scheduler-driven recovery, and clear CLOSED/OPEN/HALF_OPEN transitions. Covers concurrency guarantees, failure classification, Spring integration via @Configuration, and when to use custom implementations versus Resilience4j. Includes complete working code with atomic counters, synchronized state transitions, and ScheduledExecutorService for time-based recovery.

    17
14. 14
    Article

    Collections·9w

    Uforwarder: Uber's Scalable Kafka Consumer Proxy for Efficient Event-Driven Microservices

    Uber has open-sourced uForwarder, a Kafka consumer proxy built to handle trillions of messages and petabytes of data daily across thousands of downstream services. It replaces direct Kafka consumer clients with a gRPC-based push interface that centralizes offset management. Key features include context-aware routing via Kafka message headers for workload isolation, an out-of-order commit tracker with dead letter queue support to prevent head-of-line blocking, auto-rebalancing based on real-time CPU/memory/throughput metrics, and a DelayProcessManager for partition-level pause/resume control. The result is improved hardware utilization, reduced consumer lag, and better workload isolation at massive scale.

    11