Microservices (Architecture)

Last updated Feb 16, 2025

The Core Concepts of microservice architecturecture are:

• Definition: Microservices are an architectural style where applications are structured as a collection of loosely coupled, independently deployable services.
• Key Architectural Layers:
  • Presentation Layer: Handles user interface and client interactions
  • Business Process Layer: Contains core business logic and workflows
  • Data Access Layer: Manages data storage and retrieval
• Communication Patterns:
  • Direct Client-to-Service: Simple point-to-point communication
  • Service-Oriented Architecture: Centralized message routing through an Enterprise Service Bus
  • API Gateway/Proxy: Modern approach with distributed service mesh

Helpful images from Microservices Udemy Courses.

• Service Boundaries:
  • Each service should have a clear, bounded context
  • Services should be sized appropriately - neither too large (Monolithic) nor too small (nano-services)
  • Data domains often define natural service boundaries
• Technical Considerations:
  • Increased network latency due to service chains
  • Trade-offs between ACID Transactions and eventual consistency
  • Need for robust service discovery and load balancing
  • Importance of fault tolerance and circuit breaking

• Edge Services: Handle external-facing concerns
• Business Process Services: Implement core domain logic
• Data Services: Manage data access and storage
• Gateway Services: Route and aggregate service calls

• Backend: Java, C#, Node.js
• Frontend: JavaScript frameworks
• Data Science: Python
• Each service can use the most appropriate technology for its specific needs

DevOps can influence microservice architecture:

• Continuous Delivery Pipeline (CI/CD):
  1. Business Input drives development
  2. Code development and review
  3. Compilation and testing
  4. Unit test execution
  5. Defect reporting and tracking
• Operational Considerations:
  • Logging and tracing across services
  • Monitoring and alerting
  • Service discovery
  • Configuration management
  • Security and access control

• Keep services autonomous and loosely coupled
• Implement robust error handling and fallback mechanisms
• Use asynchronous communication where possible
• Maintain comprehensive service documentation
• Implement proper versioning strategies
• Consider implementing circuit breakers for fault tolerance

• Increased operational complexity
• Network latency and reliability concerns
• Data consistency across services
• Service discovery and routing
• Monitoring and debugging distributed systems
• Team organization and communication

• Microservices Udemy Course

Origin: Microservices Udemy Course
References: SOA
Created