Why Microservices Are the Key to Rapidly Responding to Change

Microservices

Software architecture is a system of various components such as web servers, application servers, databases, storage, and communication layers that interact with each other and the environment. The goal of system architecture is to address stakeholder concerns.

Conway’s law: Organizations which design systems are constrained to produce designs which are copies of the communication structures of these organizations.

Monolithic Architecture

Monolithic is suitable for small projects. Advantages: simple development, centralized management, little duplicate work, and all functionality resides locally without distributed overhead.

Disadvantages for internet companies include low development efficiency, difficult maintenance, inflexible deployment, low stability, and insufficient scalability.

Microservice Architecture

Microservices are small, independently deployable services that encapsulate a single business capability and communicate via lightweight mechanisms. They are loosely coupled, have bounded contexts, and align with Domain‑Driven Design principles.

Key characteristics:

Small services focusing on a single responsibility.

Independent deployment and scaling.

Independent development and evolution with flexible technology choices.

Independent teams and autonomy.

The idea is to decouple work, reduce waste, and enable rapid response to change.

"Make our system respond to change as quickly as possible" – Rebecca Parsons

Microservices aim to achieve low‑cost, fast response to change, building on decades of agile and lean practices.

Autonomous A microservice is a unit of functionality providing an API for capabilities around a business domain.

Isolated A microservice can be modified, tested and deployed independently.

Elastic A microservice is stateless and can be horizontally scaled up or down.

Resilient Designed for failure, it is fault‑tolerant and highly available.

Responsive Responds to requests in a reasonable amount of time.

Intelligent Intelligence resides in the microservice endpoints, not on the wire.

Message Oriented Microservices rely on HTTP or a lightweight message bus, ensuring loose coupling, isolation, and location transparency.

Programmable Microservices provide APIs for developers and administrators.

Composable Applications are composed from multiple microservices.

Automated The lifecycle is managed through automation covering development, build, test, staging, production, and distribution.

Service Communication

Synchronous calls are simple and provide strong consistency but can cause performance problems, especially with deep call stacks. REST over HTTP is widely accepted and language‑agnostic, while RPC offers higher efficiency and tighter security when a unified framework exists. Asynchronous messaging reduces coupling and provides buffering, at the cost of eventual consistency, the need for idempotent processing, and a dedicated broker.

Microservice Advantages

Each service is small and focuses on a specific business function.

Small teams (2‑5 developers) can develop services independently.

Loose coupling; services are independent in development and deployment.

Services can be written in different languages.

Facilitates automated deployment via CI tools such as Jenkins or Bamboo.

New team members can become productive quickly.

Individual services are easy to understand, modify, and maintain.

Enables adoption of the latest technologies.

Business logic stays separate from UI concerns.

Services can be scaled on demand.

Can run on modest hardware.

Easy third‑party integration.

Each service can have its own storage, or share a unified database.

Microservice Disadvantages

May introduce operational overhead.

Requires DevOps skills.

Potentially doubles effort.

Distributed systems can be complex to manage.

Tracing issues across services is harder.

Complexity grows as the number of services increases.

Considerations

While each service is small, overall system complexity remains; assembling many pieces is harder than a monolith.

Independent services increase inter‑service communication; efficient clustering mechanisms become essential.

Service lifecycle management (start/stop, placement) requires robust versioning and deployment tooling.

Multiple instances enable load balancing and high availability, but demand sophisticated monitoring and traffic routing.

A unified entry point (API gateway) is needed for service registration, discovery, and routing.

Enterprise concerns such as centralized security, fault auditing, system monitoring, and dependency management must be addressed at the platform level.

API Importance

• Core expression of service value • Reliable, usable, readable • One chance to get it right

Implement an API gateway as the single entry point for all clients. The gateway can proxy/route requests to appropriate services or forward them to a set of services, enforce security, and provide client‑specific APIs.

Design Elements

• Version • RequestID • Auth & Signature • RateLimit • Docs • ErrorCode & Message

Microservice Governance

• Elastic scaling – deployment and operational cost • Independent deployment – machine count and cost • Business independence – service dependencies, versioning, transaction handling • Technology diversity – environment and convention costs

• Runtime governance – monitoring, throttling, SLA, load balancing, log analysis • Service registration & discovery • Deployment – rapid, copy, scale, single‑machine development • Invocation – security, fault tolerance, degradation, latency

Service Fault Tolerance

In a microservice environment, complex dependencies can cause cascading failures; proper fault isolation and resilience are required to avoid system‑wide outages.

Service Framework

Service registration, discovery, load balancing, and health checks.

Monitoring and logging, exposing metrics and trace data.

REST/RPC and serialization support.

Configuration management, including dynamic runtime config.

Rate limiting and circuit breaking.

Management interfaces (e.g., Spring Boot Actuator).

Unified error handling.

Security plugins.

Automatic documentation generation (e.g., Swagger).

Microservice System Foundations

A minimal foundation includes logging & audit, monitoring & alerting, a message bus, service registry, load balancing, deployment & upgrade, event scheduling, and resource management.

Authentication & authorization (optional).

Unified code framework supporting multiple languages.

Unified build & packaging.

Unified testing.

CI/CD pipeline.

Service dependency management.

Unified tracing.

Canary releases.

Blue‑green deployment.

Containers (Docker) and Microservices

Containers are small, independent, provide identical development and production environments, are cost‑effective, package code and image together, and support horizontal and vertical scaling.

Containers (Docker) Management

Image management, system security, authorization, maturity, and community support.

Impact of Development Approach

Continuous delivery and Docker popularize containerized microservices, leading to a new development model that combines microservices, APIs, and platforms.

Traditional monolithic DevOps teams span product, development, QA, DBA, and operations, whereas microservice‑oriented teams separate product groups (focused on specific services) from a platform team that handles operations, communicating via APIs.

Key steps: build DevOps capability, enable continuous evolution, align teams and architecture, and foster a self‑organizing culture for sustainable microservice adoption.

Prerequisite: solid operational capabilities (monitoring, fast configuration, rapid deployment). Infrastructure‑as‑code practices help achieve consistency across environments.

Docker enables heterogeneous technology stacks (Node.js, Java, Ruby, Python) each with its own delivery lifecycle.

Microservice Cases

Netflix architecture emphasizes global distribution, high scalability, and availability.

Twitter architecture focuses on efficient, scalable data centers.

Source: https://www.cnblogs.com/wintersun/p/6219259.html