Microservices Architecture in Cloud Questions and Answers for Viva

Answer-1: Microservices architecture is an approach to designing software applications as a collection of small, loosely coupled, independently deployable services.

Answer-2: Monolithic architecture is a single unified codebase, while microservices break an application into independent services that communicate via APIs.

Answer-3: Because they allow scalable, flexible, and independent deployment, fitting well with cloud?s elasticity and distributed nature.

Answer-4: Key characteristics include decentralized data management, independent deployment, fault isolation, and technology diversity.

Answer-5: They communicate via lightweight protocols such as HTTP/REST, gRPC, or messaging queues.

Answer-6: Service discovery enables microservices to dynamically find and communicate with each other in a distributed environment.

Answer-7: API Gateway acts as a single entry point, routing requests to appropriate microservices and handling concerns like security and rate limiting.

Answer-8: Benefits include scalability, resilience, faster deployment, technology flexibility, and easier maintenance.

Answer-9: Challenges include complexity in communication, data consistency, testing, deployment, and monitoring.

Answer-10: By isolating failures to individual services, preventing cascading failures across the entire application.

Answer-11: Containers package microservices with dependencies, ensuring consistent and isolated runtime environments across clouds.

Answer-12: Each microservice manages its own database to ensure loose coupling and data ownership.

Answer-13: A consistency model where updates propagate asynchronously, meaning data may be temporarily inconsistent but will eventually converge.

Answer-14: Kubernetes, Docker Swarm, and AWS ECS are common orchestration tools managing containerized microservices.

Answer-15: Using distributed transactions or compensating transactions patterns, like the Saga pattern.

Answer-16: A design pattern that manages long-running transactions and data consistency by breaking them into a series of local transactions.

Answer-17: Through API authentication/authorization, service mesh policies, encryption, and network segmentation.

Answer-18: An infrastructure layer for managing service-to-service communications, providing load balancing, authentication, and observability.

Answer-19: They promote continuous integration/continuous deployment (CI/CD) by enabling independent service updates.

Answer-20: Centralized logging aggregates logs from different services for monitoring, debugging, and troubleshooting.

Answer-21: A technique to track requests as they flow through multiple microservices to identify latency and errors.

Answer-22: By maintaining backward compatibility and using versioning strategies such as URL versioning or header versioning.

Answer-23: Synchronous (HTTP/REST) and asynchronous (message queues, event-driven) communication.

Answer-24: Microservices allow scaling of individual components independently based on load, optimizing resource use.

Answer-25: Using unit tests for individual services, integration tests for service interactions, and end-to-end tests for workflows.

Answer-26: CI/CD automates building, testing, and deploying microservices independently and frequently.

Answer-27: A design pattern to translate between different service models to avoid dependencies on legacy systems.

Answer-28: Using centralized configuration services or environment variables managed per service.

Answer-29: Operations that produce the same result no matter how many times they are performed, crucial for reliable communication.

Answer-30: Microservices are a key part of cloud-native architecture, designed to fully exploit cloud features like elasticity and resilience.

Answer-31: An architecture where microservices communicate by producing and consuming events asynchronously.

Answer-32: By enabling independent updates, reducing deployment risks, and shortening release cycles.

Answer-33: Microservices are independent services in a distributed system; microkernel is a modular core system with pluggable components.

Answer-34: A strategy to gradually replace legacy monolithic systems by incrementally adding microservices.

Answer-35: Using event sourcing, compensating transactions, and eventual consistency models.

Answer-36: To distribute client requests evenly across service instances to ensure availability and performance.

Answer-37: By implementing retries, circuit breakers, fallbacks, and bulkheads.

Answer-38: A pattern that stops sending requests to a failing service to prevent cascading failures.

Answer-39: Using container orchestration platforms, serverless services, or managed container services.

Answer-40: Horizontal scaling adds more instances; vertical scaling adds more resources to existing instances.

Answer-41: By enabling parallel development and independent deployment of small services.

Answer-42: A database of service instances used for service discovery.

Answer-43: Keep services small, loosely coupled, independent, with clear APIs and owned data.

Answer-44: Using shared services or middleware for logging, authentication, and monitoring.

Answer-45: An approach to design microservices based on business domains and bounded contexts.

Answer-46: By keeping microservices stateless and storing state externally if needed.

Answer-47: Synchronous waits for a response (e.g., REST), asynchronous does not wait and uses events or queues.

Answer-48: Failures in one service do not affect others due to service boundaries and independent deployments.

Answer-49: Centralized monitoring with metrics, logs, traces, and alerting using tools like Prometheus and Grafana.

Answer-50: By supporting multiple API versions and ensuring changes do not break existing consumers.