Cloud Architecture Patterns (Monolithic, Microservices) Questions and Answers for Viva

Answer-1: A monolithic architecture is a single unified software application where all components are interconnected and managed as a single unit.

Answer-2: Microservices are a cloud architecture pattern where an application is divided into small, independent services that communicate over APIs.

Answer-3: Simple development and deployment, easier debugging, and less operational overhead.

Answer-4: Difficult to scale, maintain, and update; a change in one part requires redeploying the entire app.

Answer-5: Each service can be scaled independently based on demand.

Answer-6: Common methods include REST APIs, gRPC, message queues, and event streaming.

Answer-7: Monolithic apps are deployed as one unit; microservices are deployed independently.

Answer-8: Complexity in deployment, service discovery, data consistency, and inter-service communication.

Answer-9: Yes, through a process called decomposition or refactoring.

Answer-10: A mechanism for dynamically locating microservice instances in a network.

Answer-11: It acts as a single entry point to multiple microservices, handling routing, security, and load balancing.

Answer-12: Microservices can isolate failures to a single service, while monolithic failure can bring down the entire app.

Answer-13: Typically, a single centralized database is used.

Answer-14: Each microservice can have its own database, enabling decentralized data management.

Answer-15: Teams can be organized around individual services, enabling independent development.

Answer-16: Synchronous (HTTP/REST) and asynchronous (message queues, events).

Answer-17: Microservices require distributed tracing and centralized logging to track multiple services.

Answer-18: A consistency model where data changes propagate asynchronously, allowing temporary inconsistencies.

Answer-19: Containers help package and deploy microservices consistently across environments.

Answer-20: Because independent services require automated CI/CD pipelines for efficient deployment.

Answer-21: Network calls between services can increase latency compared to in-process calls in monoliths.

Answer-22: DDD is an approach to design microservices around business domains.

Answer-23: Through API security, authentication, authorization, and secure service-to-service communication.

Answer-24: They can, but scaling requires scaling the entire app, which is less efficient.

Answer-25: A technique to gradually replace parts of a monolithic app with microservices.

Answer-26: A layer that translates between legacy systems and new microservices to prevent coupling.

Answer-27: Handling transactions across services and maintaining data consistency.

Answer-28: Centralized logging aggregators collect logs from multiple services for analysis.

Answer-29: A design pattern to handle service failures gracefully by stopping calls to failing services temporarily.

Answer-30: Services are versioned independently to manage backward compatibility.

Answer-31: To automate deployment, scaling, and management of containers and services.

Answer-32: Kubernetes, AWS ECS/EKS, Azure AKS, Google Kubernetes Engine.

Answer-33: Complex integration testing due to multiple independent services.

Answer-34: Failures in one service do not directly impact others.

Answer-35: Leads to polyglot persistence, where different services use different databases.

Answer-36: Small to medium applications with limited complexity and lower scalability needs.

Answer-37: By vertical scaling (increasing resources of a single server).

Answer-38: A dedicated infrastructure layer for handling service-to-service communication, security, and observability.

Answer-39: Ensuring data consistency and minimizing downtime during transition.

Answer-40: Using distributed transactions or eventual consistency with compensating actions.

Answer-41: It enables asynchronous communication and decouples services.

Answer-42: Microservices enable more frequent and independent deployments.

Answer-43: By isolating faults and enabling retries or fallback mechanisms.

Answer-44: Increased operational complexity and resource usage may raise costs.

Answer-45: Microservices require more complex observability with tracing and metrics across services.

Answer-46: Microservices can increase productivity by enabling smaller focused teams.

Answer-47: A boundary defining a microservice?s domain and responsibilities.

Answer-48: By supporting multiple versions simultaneously and deprecating older versions gradually.

Answer-49: To improve performance by reducing redundant calls to services or databases.

Answer-50: Monoliths offer simplicity and ease of deployment; microservices provide scalability, flexibility, and fault isolation but with increased complexity.