Best of Microservices — October 2025

  1. 1
    Video
    Avatar of letsgetrustyLet's Get Rusty·25w

    Rust intern saved TikTok $300K

    A TikTok intern rewrote CPU-intensive payment service endpoints from Go to Rust, reducing average latency by 30%, P99 latency by 76%, and cutting compute costs by 50%—saving $300K annually. The migration used a gradual rollout strategy with separate Rust clusters under the same service name, avoiding upstream code changes. Key challenges included adapting Go's zero values to Rust's Option enum and optimizing memory allocations. The main lesson: Rust delivers performance gains at the cost of developer productivity, making it ideal for high-usage, stable components where economies of scale justify the rewrite effort.

  2. 2
    Video
    Avatar of codeheadCodeHead·26w

    99% Of Devs Don't Understand Spring Boot

    Spring Boot simplifies Java development by automating configuration and removing XML complexity, making it production-ready out of the box. Major companies like Netflix, Amazon, and Spotify rely on it to power massive-scale systems with billions of API calls daily. Modern versions support Kotlin, reactive programming through Spring WebFlux, and cloud-native deployments, making it more relevant than its outdated reputation suggests. The framework's strength lies in its reliability, comprehensive ecosystem, and ability to handle enterprise-scale workloads efficiently.

  3. 3
    Article
    Avatar of systemdesigncodexSystem Design Codex·26w

    Authorizing 10 Million API Calls Per Second

    LinkedIn handles authorization for tens of millions of API calls per second using Access Control Lists (ACLs) with an in-memory authorization client on each service. ACL data is stored in Espresso database with Couchbase caching, synchronized via Brooklin change data capture. Authorization checks are logged asynchronously through Kafka for monitoring and auditing. The system balances fast authorization checks, timely ACL updates, efficient data management, and comprehensive monitoring at massive scale.

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

    A must-read book - Architecture for Flow: Adaptive Systems with Domain-Driven Design, Wardley Mapping, and Team Topologies

    A recommendation for Susanne Kaiser's book that combines Domain-Driven Design, Wardley Mapping, and Team Topologies to build adaptive systems. The book addresses how IT organizations can adapt quickly in volatile business environments by applying these three methodologies together to achieve fast flow and organizational agility.

  5. 5
    Article
    Avatar of flipkartFlipkart Tech·26w

    Unifying the Gates: Building Flipkart’s Centralized API Gateway for 10x Scale

    Flipkart built Nexus, a centralized API gateway using open-source APISIX, to replace their fragmented infrastructure where each team managed separate gateway functions. The solution consolidates authentication, rate-limiting, and session management into a unified platform achieving 99.99% availability with sub-10ms p99 latency overhead. The three-plane architecture (management, control, and data planes) uses etcd for real-time configuration updates and deploys across multiple data centers for high availability. The MART organization serves as a case study, showing how Nexus eliminated redundant systems and standardized API management across diverse channels.

  6. 6
    Video
    Avatar of continuousdeliveryContinuous Delivery·30w

    Why Are Software Engineers Quitting Microservices?

    Explores the recent discourse around developers abandoning microservices, analyzing whether this trend is real and justified. Examines a widely-cited Amazon case study that moved from microservices to a monolith, questioning whether their original implementation was truly microservices-based. Discusses the inherent complexity of microservices, including distributed systems challenges, the need for sophisticated development practices like continuous delivery and contract testing, and proper service boundaries aligned with business capabilities. Argues that microservices remain the best solution for scaling development teams but come with significant overhead that makes them unsuitable for small teams, emphasizing that success requires careful design of service interfaces and organizational decentralization.

  7. 7
    Article
    Avatar of zaidesantonManager.dev·26w

    Give your engineers a kingdom

    Engineering managers often become bottlenecks by centralizing all decisions and prioritization. As teams mature, managers should distribute ownership by assigning engineers specific 'kingdoms' - areas like applications, microservices, third-party integrations, or critical tools. Kingdom owners make decisions, prioritize work, monitor health, and serve as go-to experts for their domain. The approach works best with 1-2 kingdoms per engineer, giving them both pride and dedicated time to manage their areas effectively. Success requires empowering engineers with decision-making authority and development time, not just dumping responsibilities.

  8. 8
    Article
    Avatar of hnHacker News·28w

    Why is everything so scalable?

    A critical examination of the trend toward over-engineering for scale in startups. The author argues that most companies prematurely adopt complex, distributed architectures (microservices, cloud infrastructure, orchestrators) designed for FAANG-scale problems they don't have. Instead, they advocate for starting with a well-structured monolith using modular design with strict interface boundaries, static typing, and enforced separation of concerns. This approach provides clean architecture, atomic deployments, better type safety, and significantly lower costs while deferring the complexity of distributed systems until actually needed.

  9. 9
    Article
    Avatar of platformaticPlatformatic·29w

    Integrate Python ASGI with Node.js Apps

    Platformatic releases @platformatic/python, enabling Python ASGI applications to run directly inside Node.js processes. The integration eliminates network overhead by using interprocess communication instead of HTTP calls between services. Built on a Rust bridge layer with the http-handler crate, it provides seamless request/response translation between Node.js and Python. Developers can embed FastAPI, Django, or custom ASGI apps alongside Node.js workloads, particularly useful for AI/ML inference, real-time data processing, and gradual migration scenarios. Benchmarks show competitive performance with traditional ASGI servers while offering microsecond-level latency through in-process architecture.

  10. 10
    Article
    Avatar of earthlyEarthly·30w

    Backstage Adoption Guide: When to Use Spotify's Developer-Portal Framework

    Based on interviews with 20+ engineering teams, this guide examines when Backstage (Spotify's open-source developer portal framework) makes sense for organizations. Backstage works best for teams with 30+ engineers, multiple microservices, and 3-5 dedicated maintainers who can handle React/TypeScript. The framework isn't free despite being open-source—expect $380-650k annually for DIY implementation versus $84k for managed alternatives. Common pitfalls include underestimating frontend skill requirements, forcing 100% adoption, and lacking executive sponsorship. Success requires focusing on specific pain points (onboarding, service scaffolding, documentation), measuring ROI through metrics like time-to-first-PR and MTTR, and treating the portal as an internal product with iterative rollouts.

  11. 11
    Article
    Avatar of Marmelabmarmelab·30w

    Do you need a Backend For Frontend?

    The Backend-for-Frontend (BFF) pattern addresses common issues in multi-client applications where frontend teams struggle with API complexity and performance problems. A BFF acts as a dedicated translation layer between frontends and backend services, aggregating data and handling client-specific logic. While it can dramatically improve development velocity and mobile performance, it's not suitable for simple applications or small teams due to increased operational complexity.

  12. 12
    Article
    Avatar of systemdesignnewsSystem Design Newsletter·26w

    How Remote Procedure Call Works

    Remote Procedure Call (RPC) enables services to communicate efficiently by making remote function calls feel like local ones. The protocol uses client stubs and server skeletons to handle marshaling, network transmission, and unmarshaling automatically. Key failure handling strategies include timeouts, retries with idempotency safeguards, circuit breakers, and deadline propagation. Real-world implementations require service discovery, backward-compatible API evolution, streaming support, and standardized error codes. While RPC offers high performance and simple programming models through frameworks like gRPC, it creates tight coupling and requires specialized tooling compared to REST APIs.

  13. 13
    Article
    Avatar of javarevisitedJavarevisited·26w

    Top 5 Frontend Masters Courses to Learn Golang in 2026

    A curated list of five Frontend Masters courses for learning Go programming in 2026, ranging from fundamentals to production-ready web applications. The guide covers beginner courses on Go basics, advanced courses on building professional web applications, full-stack development with vanilla JavaScript, backend architecture patterns, and essential Linux command-line skills. Includes recommended learning paths for different career goals (beginner, full-stack, backend architecture, DevOps) and practical advice on maximizing the learning experience through hands-on projects and consistent practice.

  14. 14
    Article
    Avatar of istioIstio·28w

    Announcing Istio 1.26.5

    Istio 1.26.5 is a patch release that includes several bug fixes and improvements. Key changes include enhanced TLS secret access controls for Kubernetes Gateway API gateways, configurable pod-to-proxy association behavior, fixes for waypoint configuration and ServiceEntry resolution in ztunnel, and removal of the installation dependency between pilot and CNI components.

  15. 15
    Article
    Avatar of freecodecampfreeCodeCamp·26w

    Serverless and Microservices with C# & Azure

    A comprehensive 2-hour video course covering serverless architecture and microservices development using C# and Azure. The course progresses from fundamental concepts to production-ready implementations, including Azure Functions, Docker containers, Kubernetes orchestration, and .NET Aspire. Topics include serverless architecture patterns, microservices design patterns, onion architecture, Azure triggers, background functions, IoT functions, and practical route planning microservices.

See all Microservices archives