Microservices & Messaging Flashcards
What are the key benefits of using microservices architecture?
Microservices offer modularity, enabling independent development, deployment, and scaling of individual services. This allows for better fault isolation, flexibility in technology choices, and enhanced scalability.
How do you handle communication between microservices?
Microservices can communicate through synchronous (HTTP/REST APIs, gRPC) or asynchronous methods (message brokers like RabbitMQ, Kafka). For decoupling and fault tolerance, asynchronous messaging is preferred in many systems.
What are some common challenges with microservices, and how do you address them?
Common challenges include:
Data consistency: Solved using distributed patterns like the Saga or Event Sourcing.
Service discovery: Solved using tools like Consul or Kubernetes for registering and finding services.
Network latency: Minimized by reducing inter-service calls or using caching.
How does the Saga Pattern work, and why is it important in microservices?
The Saga Pattern manages distributed transactions in microservices. It divides a long transaction into smaller steps, with compensating transactions if one step fails. This ensures consistency across multiple services without using a traditional two-phase commit.
How do you monitor and maintain the health of your microservices?
Monitoring tools like Prometheus, Grafana, or ELK stack (Elasticsearch, Logstash, Kibana) are used to monitor service performance, logs, and health checks. Implementing endpoint checks (e.g., /health) for each service is also common.
