microservicebased

Microservicebased, commonly described as microservice-based architecture, is an approach to building software as a suite of small, independently deployable services that implement distinct business capabilities. Each service runs in its own process and communicates with others through lightweight protocols, typically HTTP/REST or messaging. Services are organized around bounded contexts and can be developed, deployed, and scaled independently.

A service typically owns its own data store, enabling decentralized data management. This avoids a single monolithic database schema and supports polyglot persistence, but it requires coordination for cross-service workflows. Distributed transactions are discouraged in favor of sagas and eventual consistency.

Advantages include independent deployment, scalability, fault isolation, and resilience, with better alignment to autonomous teams. It enables faster delivery and technology flexibility for each service.

Challenges include operational complexity, need for comprehensive monitoring and tracing, testing across services, and deployment coordination. Network latency, partial failures, data consistency, security, and versioning require mature DevOps practices.

Patterns and tooling include API gateways, service discovery, load balancing, circuit breakers, event-driven messaging, domain events, and sagas. Infrastructure commonly uses containers, Kubernetes, and service meshes for secure, observable inter-service communication.

Organizational and governance aspects require teams aligned to business capabilities, standardized interfaces, and strong CI/CD. While well suited to cloud-native, large-scale systems, misalignment can increase cost and complexity.

See also microservices, distributed architecture.