Microservices

(OBJ 3.1)

Architectural style for breaking down large applications into small, independent services
- Provides scalability and flexibility
Each microservice runs a unique process and communicates through a well-defined, lightweight mechanism
Contrasts with traditional monolithic architecture, where all components are interconnected and interdependent
Each service in the microservice architecture is self-contained and able to run independently
Example:
- Netflix - the global streaming giant streaming billion hours of content a week
- Each microservice was designed for a specific purpose
  - Recommendations
  - Video encoding
  - etc.

Scalability
- Services can be scaled independently based on demand
- Beneficial for large applications where certain modules may have more traffic or require more resources
Flexibility
- Microservices can use different technologies and be managed by different teams
Resilience
- Isolation reduces the risk of system-wide failures
Faster Deployments and Updates
- Independent deployment and updates allow for agility and reduced deployment risk

Complexity
- Managing multiple services involves inter-service communication, data consistency, and distributed system testing
Data Management
- Each microservice can have its own database, leading to data consistency challenges
Network Latency
- Increased inter-service communication can result in network latency and slower response times
Security
- The distributed nature of microservices increases the attack surface, requiring robust security measures