Best of Microservices — September 2025

  1. 1
    Article
    Avatar of systemdesignnewsSystem Design Newsletter·33w

    7 Best Practices for API Design 🔥

    Seven essential practices for designing robust APIs: REST fundamentals for organizing data resources, proper error handling with clear status codes, API versioning for backward compatibility, rate limiting to prevent abuse, pagination techniques (offset vs cursor) for large datasets, idempotency to avoid duplicate processing, and filtering/sorting for efficient data retrieval. Each practice includes implementation details and trade-offs to consider.

  2. 2
    Video
    Avatar of techworldwithnanaTechWorld with Nana·33w

    Learn Docker in 2025 - Complete Roadmap Beginner to Pro

    A comprehensive Docker learning roadmap that takes beginners through containerization fundamentals, from understanding the 'it works on my machine' problem to advanced production practices. Covers essential concepts including Docker images, containers, Dockerfile creation, Docker Compose for multi-container applications, networking, volumes for data persistence, and production best practices like security scanning and multi-stage builds. Also introduces container orchestration with Kubernetes as the natural next step for scaling containerized applications.

  3. 3
    Video
    Avatar of codeheadCodeHead·33w

    Should YOU Become a Backend Dev?

    Backend development in 2025 involves managing complex microservices architectures, cloud infrastructure, AI integrations, and security concerns. While the core responsibilities remain building APIs and managing databases, developers now juggle dozens of services, navigate extensive cloud platforms like AWS, and handle AI model integrations. The role has expanded to include security engineering responsibilities, with constant focus on preventing data breaches. Despite the challenges of debugging distributed systems and handling 3 AM alerts, backend developers remain essential for keeping internet infrastructure running smoothly.

  4. 4
    Article
    Avatar of muratbuffaloMetadata·33w

    Disaggregation: A New Architecture for Cloud Databases

    Disaggregated database architecture separates compute and storage into independent, scalable components to better exploit cloud elasticity. This approach addresses the asymmetry between expensive, fluctuating compute resources and cheaper, stable storage. Modern systems like Snowflake and Aurora demonstrate this pattern, with newer implementations pushing disaggregation further into specialized services. While disaggregation enables better resource utilization and cost optimization, it introduces performance tradeoffs due to network communication overhead. The architecture also opens opportunities to rethink distributed protocols and enables new capabilities like real-time HTAP systems and specialized hardware adoption.

  5. 5
    Article
    Avatar of platformaticPlatformatic·34w

    Watt 3: Serving Node.js Applications

    Watt 3 is a major release of the Node.js Application Server featuring parallel application startup/shutdown for faster deployments, native TypeScript support through type stripping, renamed composer to gateway for better API gateway functionality, and architectural modernization with ESM modules and Node.js 22+ requirement. The release includes 15 breaking changes, unified CLI experience, clearer terminology (capabilities instead of stackables), and extraction of client generation into standalone Massimo project.

  6. 6
    Article
    Avatar of bytebytegoByteByteGo·30w

    How Grab’s Migration from Go to Rust Cut Costs by 70%

    Grab successfully migrated their Counter Service from Go to Rust, achieving a 70% cost reduction through improved resource efficiency. While latency remained similar, the Rust version required only 4.5 CPU cores compared to Go's 20 cores for handling 1,000 requests per second. The migration involved careful library selection, rebuilding internal tools like configuration systems, and overcoming challenges with Rust's borrow checker and async concurrency model.

  7. 7
    Article
    Avatar of systemdesigncodexSystem Design Codex·32w

    Most Important Tips for System Design Interviews

    A comprehensive guide covering 23 essential principles for system design interviews, including scaling strategies (vertical then horizontal), caching for read-heavy systems, database optimization techniques, load balancing, and architectural patterns. Emphasizes the importance of clarifying requirements, considering trade-offs, and maintaining interactive communication during interviews rather than seeking perfect solutions.

  8. 8
    Article
    Avatar of confConfluent Blog·30w

    Why Microservices Need Event-Driven Architectures for Agility and Scale

    Event-driven architectures solve critical problems in microservices by replacing synchronous API calls with asynchronous event communication. This approach eliminates bottlenecks, prevents cascading failures, and enables real-time responsiveness. Apache Kafka serves as the central platform for event streaming, allowing services to publish and subscribe to events independently. The shift from REST-based to event-driven microservices delivers faster innovation cycles, improved system resilience, and better customer experiences across industries like finance, e-commerce, and telecommunications.

  9. 9
    Article
    Avatar of systemdesigncodexSystem Design Codex·30w

    How Amazon S3 Works Behind the Scenes

    Amazon S3 processes millions of requests per second and stores over 350 trillion objects using a microservices architecture. The system consists of five main layers: front-end services for request handling and authentication, metadata services for object indexing, storage services using erasure coding across multiple availability zones, durability services with checksums and auditing, and security services with IAM policies and encryption. This modular approach enables independent scaling and updates while achieving 11 nines of durability.

  10. 10
    Article
    Avatar of thebluegroundengBlueground Engineering·32w

    A Software Engineer’s Guide to Observability

    A comprehensive guide to observability for engineering teams, covering the three pillars (logging, tracing, metrics) and their practical applications. Explains why observability has become critical in the era of distributed systems and AI-generated code, where complexity is increasing while domain expertise is becoming more distributed. The guide focuses on understanding when and why to use different observability tools rather than just how to configure them.

  11. 11
    Article
    Avatar of microservicesioMicroservices.io·32w

    Authentication and authorization in a microservice architecture - Part 4 - fetching and replicating authorization data

    Explores two strategies for handling remote authorization data in microservices: fetch and replicate. The fetch strategy involves making HTTP calls or using the Saga pattern to retrieve authorization data from other services, while the replicate strategy uses CQRS to maintain local copies of authorization data synchronized through events. Each approach has trade-offs between simplicity, runtime coupling, and data freshness.

  12. 12
    Article
    Avatar of techworld-with-milanTech World With Milan·31w

    Scale from zero to million users on Azure

    A comprehensive guide to scaling applications from single users to millions on Azure, covering architectural evolution through six stages. Explores key concepts including stateless design, caching strategies, load balancing, database scaling, microservices decomposition, and multi-region deployment. Details Azure-specific services like App Service, SQL Database, Redis Cache, Front Door, and Cosmos DB for each scaling phase, with practical trade-offs between consistency and availability at global scale.

  13. 13
    Article
    Avatar of infoworldInfoWorld·31w

    Advanced debug logging techniques: A technical guide

    Debug logging is essential for maintaining high-performance applications across different architectures. Effective debug logging requires being selective about what to log, using structured formats like JSON, including contextual information such as correlation IDs, and implementing techniques like parameterized logging and rate limiting. Key practices include avoiding over-logging, never logging sensitive data, maintaining consistent formatting, and using centralized log management platforms. The guide covers specific tools for different languages (Winston for Node.js, structlog for Python, SLF4J for Java) and emphasizes the importance of correlation IDs for distributed tracing in microservice environments.

  14. 14
    Article
    Avatar of last9Last9·32w

    Kubernetes Service Discovery Explained with Practical Examples

    Kubernetes service discovery enables applications to find and communicate with each other in dynamic container environments. Services provide stable network abstractions over ephemeral Pods using DNS resolution and label selectors. The guide covers practical examples including internal communication, external access via Ingress, headless services for direct Pod access, and troubleshooting common issues like DNS resolution failures and missing endpoints.

  15. 15
    Video
    Avatar of codeheadCodeHead·33w

    Spring Boot Explained In 2 minutes

    Spring Boot is a Java framework that simplifies application development by providing auto-configuration, embedded servers, and starter dependencies. It eliminates the complexity of traditional Java web app setup, allowing developers to create REST APIs with minimal code. Major companies like Netflix, Amazon, and JP Morgan Chase use Spring Boot in production for enterprise applications.

See all Microservices archives