Best of Microservices.io — 2024

  1. 1
    Article
    Avatar of microservicesioMicroservices.io·2y

    The evolution of the Microservice Architecture pattern language

    The post discusses the evolution of the Microservice Architecture pattern language over the past decade, highlighting its origins and development. It introduces essential concepts like anti-patterns, the forces of dark energy and dark matter in architectural decisions, and the importance of context in determining architectural choices. Additionally, it advises on refining terminology and emphasizes that monolithic architectures remain useful in many contexts. Future improvements and ongoing adaptation in the field are also covered.

  2. 2
    Article
    Avatar of microservicesioMicroservices.io·2y

    Microservices rules: what good looks like

    11 development and architecture rules for successful adoption of microservices are presented in this post.

  3. 3
    Article
    Avatar of microservicesioMicroservices.io·2y

    Architectural patterns for modular monoliths that enable fast flow

    Explore three architectural patterns for building modular monoliths aimed at achieving fast flow: the modular monolith (domain-oriented monolith), domain module API, and domain API build module. These patterns help manage complexity, enhance team autonomy, and expedite the deployment pipeline. Attend the workshop 'Architecting for fast flow' to delve deeper into these techniques.

  4. 4
    Article
    Avatar of microservicesioMicroservices.io·2y

    Architecting microservices for fast, sustainable flow

    Microservice architecture structures an application as multiple loosely design-time coupled and independently deployable services. This approach facilitates faster deployment pipelines, better observability, and simplifies the evolution of the technology stack. However, it demands careful design to ensure loose coupling and stable APIs, and requires cultural changes in testing and deployment practices. Starting with a monolith may be advisable in new domains to identify stable APIs before transitioning to microservices.

  5. 5
    Article
    Avatar of microservicesioMicroservices.io·2y

    Reducing insider trading in a microservice architecture

    Reducing insider trading in microservice architectures involves ensuring loose design-time coupling by avoiding direct database queries between services and using APIs instead. However, APIs alone don't guarantee loose coupling. Encapsulation is crucial, where each service hides its internal data and logic, resembling icebergs. This approach, applied in examples like takeout burritos, helps manage dependencies and improve the maintainability of the system.

  6. 6
    Article
    Avatar of microservicesioMicroservices.io·2y

    Microservices rules #10: Make smaller, safer, and reversible changes - part 3

    Making smaller, safer, and reversible changes is crucial for the production deployment of microservices. This approach minimizes risks and ensures system stability.

  7. 7
    Article
    Avatar of microservicesioMicroservices.io·2y

    Architecting monoliths for fast, sustainable flow

    Fast, sustainable flow is the continuous delivery of valuable changes while keeping the technology stack current, requiring team-sized elements, loose coupling, testability, deployability, observability, and evolvability. While monolithic architectures can be simpler than microservices, they often struggle with evolvability and deployment pipeline bottlenecks, but careful design can overcome some limitations. The upcoming workshop covers architectural design, trade-offs, and strategies to enhance fast, sustainable flow.

  8. 8
    Article
    Avatar of microservicesioMicroservices.io·2y

    Architecture is multi-dimensional

    Architecture is multi-dimensional and can be defined as the decomposition into parts and relationships. The classic 4+1 view model describes architecture using 5 views. The author prefers describing architecture with dimensions including Domain, Component, Deployment, and Pipeline. The success triangle focuses on component and deployment pipeline architectures.

  9. 9
    Article
    Avatar of microservicesioMicroservices.io·2y

    Microservices rules #10: Make smaller, safer, and reversible changes - part 1

    Discusses the importance of making smaller, safer, and reversible changes in microservices architecture. Highlights strategies to improve the flow of development and integrate DevOps and Team Topologies principles. Includes information about upcoming public workshops on these topics.

  10. 10
    Article
    Avatar of microservicesioMicroservices.io·2y

    Evolving an architecture: a problem solving-driven approach

    Explore how to evolve a software architecture using a problem-solving driven approach. Learn from real-world scenarios, such as handling more services than teams after layoffs, and discover frameworks that enable effective architectural decisions.

  11. 11
    Article
    Avatar of microservicesioMicroservices.io·2y

    A better way to think about developer productivity metrics

    The post discusses developer productivity metrics and how they actually measure the productivity of the socio-technical system rather than the developers themselves.

See all Microservices.io archives