Monolithic vs. Microservices Questions and Answers for Viva

Answer-1: Monolithic architecture is a software design pattern where all components are combined in a single unit.

Answer-2: Microservices architecture involves designing an application as a collection of loosely coupled services.

Answer-3: Monolithic combines all components; Microservices separate functionalities into individual services.

Answer-4: Easier deployment, simpler development, and centralized management.

Answer-5: Difficult to scale, tightly coupled components, and maintenance challenges as the system grows.

Answer-6: Scalability, flexibility, and independent deployment.

Answer-7: Increased complexity, network latency, and higher development costs.

Answer-8: For small to medium-sized applications with fewer modules and lower complexity.

Answer-9: For large-scale, complex applications requiring scalability and independent service management.

Answer-10: Includes data management, inter-service communication, and system re-architecture.

Answer-11: Typically using REST APIs, gRPC, or messaging systems like RabbitMQ or Kafka.

Answer-12: An API gateway manages requests, handles authentication, and routes traffic to services.

Answer-13: A mechanism where microservices register themselves and discover each other dynamically.

Answer-14: Docker, Kubernetes, Consul, Eureka, and Spring Boot are commonly used tools.

Answer-15: Microservices scale independently, while monolithic scaling often requires replicating the entire application.

Answer-16: DevOps practices like CI/CD pipelines are essential for managing the complexity of microservices deployments.

Answer-17: Each microservice may have its own database, ensuring data isolation and service independence.

Answer-18: By implementing techniques like circuit breakers, retries, and fallbacks.

Answer-19: Includes integration testing, service isolation, and ensuring communication between services works correctly.

Answer-20: Yes, in some cases, services may interact with in-memory data or external APIs instead of databases.

Answer-21: Each microservice is designed to perform one specific task or functionality.

Answer-22: Monolithic requires entire application deployment; microservices allow independent service deployment.

Answer-23: Tools like Docker enable packaging services with their dependencies for easy deployment and scalability.

Answer-24: It defines the boundary within which a microservice operates and owns its data.

Answer-25: Synchronous (REST, gRPC) and asynchronous (message queues, event-driven) communication are common.

Answer-26: Response time, error rate, throughput, and resource utilization are common metrics.

Answer-27: Managing and coordinating services using tools like Kubernetes for automated workflows.

Answer-28: Shared databases, tightly coupled services, and improper service boundaries.

Answer-29: A design pattern where an auxiliary service runs alongside the primary service to handle supporting tasks.

Answer-30: Distributes incoming traffic among services using algorithms like round-robin or least connections.

Answer-31: A design where services communicate by producing and consuming events asynchronously.

Answer-32: A monorepo contains all services in one repository, while microservices usually have separate repositories.

Answer-33: Using authentication mechanisms like OAuth2, JWT, and mutual TLS.

Answer-34: Logging ensures observability and debugging by tracking service interactions and errors.

Answer-35: Using eventual consistency, distributed transactions, or sagas.

Answer-36: Versioning ensures backward compatibility and smooth updates for dependent services.

Answer-37: It allows each service to use the most appropriate language or framework for its requirements.

Answer-38: Gradually replacing monolithic components with microservices while maintaining functionality.

Answer-39: Monolithic has faster initial development; microservices allow parallel team contributions.

Answer-40: The ability of the system to continue functioning despite failures in individual services.

Answer-41: Using centralized configuration tools like Consul or Spring Cloud Config.

Answer-42: A practice of maintaining different versions of APIs to ensure compatibility.

Answer-43: Uncontrolled growth of services leading to complexity and management challenges.

Answer-44: A dedicated infrastructure layer for managing service-to-service communication.

Answer-45: Caching can be applied per service to reduce latency and improve performance using tools like Redis.

Answer-46: A strategy where two environments (blue and green) are used to deploy and test services with zero downtime.

Answer-47: By using redundancy, failover mechanisms, and distributed systems.

Answer-48: Microservices require more granular monitoring, while monolithic focuses on overall performance.

Answer-49: Spring Boot, Django, Express.js, and Flask are commonly used frameworks.

Answer-50: Enables decoupled communication between services, improving scalability and resilience.