Which architecture emphasizes independently deployable services with lightweight interfaces?

Which architecture emphasizes independently deployable services with lightweight interfaces?

• A. Microservices
• B. Infrastructure as Code
• C. Service-Oriented Architecture
• D. Client-Server

Answer: (A)

Microservices architecture emphasizes breaking a system into small, independently deployable services that communicate through lightweight interfaces. Each service focuses on a specific capability and can be developed, tested, deployed, and scaled on its own, without requiring the others to be updated. This autonomy enables teams to iterate faster and roll out changes with less risk, since a failure in one service doesn’t directly bring down the whole system. Communication between these services uses simple, lightweight protocols—such as HTTP/REST, messaging queues, or gRPC—keeping the interfaces small and well-defined. Because each service owns its own data and logic, you get better fault isolation and the ability to scale parts of the system that have higher demand. This differs from heavier, enterprise-oriented approaches that try to expose services through a central integration layer or shared data models. While service-oriented architecture also uses services, microservices push for even finer-grained boundaries and more decentralized governance, prioritizing independently deployable units and lightweight, loosely coupled interfaces.

Microservices architecture emphasizes breaking a system into small, independently deployable services that communicate through lightweight interfaces. Each service focuses on a specific capability and can be developed, tested, deployed, and scaled on its own, without requiring the others to be updated. This autonomy enables teams to iterate faster and roll out changes with less risk, since a failure in one service doesn’t directly bring down the whole system.

Communication between these services uses simple, lightweight protocols—such as HTTP/REST, messaging queues, or gRPC—keeping the interfaces small and well-defined. Because each service owns its own data and logic, you get better fault isolation and the ability to scale parts of the system that have higher demand.

This differs from heavier, enterprise-oriented approaches that try to expose services through a central integration layer or shared data models. While service-oriented architecture also uses services, microservices push for even finer-grained boundaries and more decentralized governance, prioritizing independently deployable units and lightweight, loosely coupled interfaces.