Interview Q&A

Short answer: re dynamic (e.g., containers that can scale in and out), hardcoding service addresses (IPs or URLs) is impractical. Service discovery ensures that microservices can dynamically find nd communicate with each other in a reliable and efficient way. Why it's important:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Service Discovery is the process of automatically detecting the network locations of services in a microservices architecture.

Explain a bit more

As services in a microservices-based application are dynamic (e.g., containers that can scale in and out), hardcoding service addresses (IPs or URLs) is impractical. Service discovery ensures that microservices can dynamically find and communicate with each other in a reliable and efficient way. Why it's important:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Load balancing is the distribution of incoming network traffic across multiple instances of a service to ensure that no single instance becomes overwhelmed. In microservices:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: A reverse proxy acts as an intermediary between clients and the services, forwarding requests from clients to the appropriate backend service instances.

Explain a bit more

Role in load balancing: Traffic Routing: The reverse proxy (e.g., Nginx, HAProxy) forwards incoming traffic to different service instances based on load balancing policies. SSL Termination: The reverse proxy can handle SSL/TLS encryption, offloading this task from the service instances, which simplifies the architecture. Health Checks: A reverse proxy can perform health checks on service instances and route traffic only to healthy instances. In a typical microservices setup, a reverse proxy like Envoy or Nginx is used to handle traffic routing and distribute the load evenly across the microservices.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: There are two main types of load balancing: client-side and server-side. Client-Side Load Balancing: The client (e.g., the microservice making the request) is responsible for deciding how to distribute requests across service instances.

Example code

In Netflix OSS, Ribbon is used for client-side load balancing, where the client has a list of service instances and decides which one to call based on various strategies (e.g., round-robin, random). Server-Side Load Balancing: A load balancer (e.g., HAProxy, Nginx, or Kubernetes LoadBalancer) is responsible for distributing traffic among service instances. The client sends all requests to the load balancer, which then routes them to appropriate instances. Example: In Kubernetes, the service uses an internal load balancer that balances traffic across multiple pods running the service.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Sticky sessions (or session affinity) are essential in cases where a service needs to maintain stateful interactions with a client across multiple requests.

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Ensuring high availability and failover in microservices involves several strategies:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Contract testing is a type of testing used to ensure that the interaction between two microservices (provider and consumer) conforms to an agreed-upon contract. This contract defines the expected request and response formats, ensuring that both services can communicate correctly, even when developed independently. Importance in Microservices:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Integration testing focuses on testing how different microservices work together within an ecosystem, simulating interactions and ensuring that services collaborate as expected. Approach:

Example code

Integration testing focuses on testing how different microservices work together within an ecosystem, simulating interactions and ensuring that services collaborate as expected. Approach:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: End-to-end (E2E) testing simulates a real-world user experience by testing the entire flow of the system from start to finish, involving all microservices, databases, and external systems. Tools:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Testing asynchronous messaging involves verifying that messages sent via queues or event-driven systems are correctly processed by the receiving services. Approach:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Mock testing involves simulating the behavior of complex or unavailable external services by creating mock objects or stubs. This is especially useful in unit testing and integration testing to isolate specific components. Approach:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Testing scalability ensures that a microservices system can handle increased load without significant degradation in performance. Approach:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Testing microservices in production presents unique challenges, as you're working with live traffic and systems. Challenges:

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Testing fault tolerance and resilience ensures that microservices can continue to function correctly even when some services or components fail. Approach:

Real-world example (ShopNest)

If Payment is down, the Order service fails fast with a circuit breaker instead of hanging every checkout thread.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Testing in a distributed system (such as microservices) is crucial for ensuring that:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: workflow engine) coordinates the interactions between different microservices.

Explain a bit more

The orchestrator is responsible for directing the flow of operations and ensuring that services interact in a specific sequence. A payment processing system where a central service coordinates interactions between multiple services like fraud detection, payment gateway, and notification service. Service Choreography: In choreography, microservices interact directly with one nother, with each service knowing how to interact with others. There is no central controller; instead, each service follows a predefined protocol or contract. dvantages: More decentralized and flexible, making it suitable for dynamic and loosely coupled services. Reduced bottlenecks and no single point of failure.

Example code

In an order processing system, services (e.g., inventory, payment, shipping) emit events that other services subscribe to and act upon, without a central orchestrator.

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Service Orchestration: In orchestration, a central component (like an orchestrator or a workflow engine) coordinates the interactions between different microservices.

Explain a bit more

The orchestrator is responsible for directing the flow of operations and ensuring that services interact in a specific sequence. Advantages: Centralized control and easy-to-manage workflows. Easier to monitor and troubleshoot because the orchestrator controls the flow. Suitable for complex workflows with well-defined sequences.

Example code

A payment processing system where a central service coordinates interactions between multiple services like fraud detection, payment gateway, and notification service. Service Choreography: In choreography, microservices interact directly with one another, with each service knowing how to interact with others. There is no central controller; instead, each service follows a predefined protocol or contract. Advantages: More decentralized and flexible, making it suitable for dynamic and loosely coupled services. Reduced bottlenecks and no single point of failure. Example: In an order processing system, services (e.g., inventory, payment, shipping) emit events that other services subscribe to and act upon, without a central orchestrator.

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Microservices are inherently well-suited to DevOps practices due to their modular and independent nature. DevOps aims to enhance collaboration between development and operations teams, and microservices support this by:

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: uthorization), rate-limiting, and caching. The gateway typically focuses on external communication and manages how clients interact with the microservices.

Real-world example (ShopNest)

ShopNest’s API Gateway routes /orders to the Order service and /payments to Payment—clients talk to one entry point.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul?

Example code

using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul? using tools like Spring Cloud or Consul?

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: And deployed. How they relate to microservices: Decoupling: Just like microservices, micro-frontends break down the application into smaller, independently deployable components. Technology Independence: Different micro-frontends can use different technologies (e.g., React, Angular, Vue) or versions of the same technology, allowing teams to… work……… independently. Autonomous Teams: Frontend teams can work…

Explain a bit more

independently on specific parts of the UI without impacting the entire application. Example: A shopping website could have separate micro-frontends for product listing, checkout, and user profile, all developed and deployed independently.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: Micro-frontends are a design approach that applies microservices principles to the front-end.

Explain a bit more

Instead of having a single monolithic front-end, the front-end is broken into smaller, self-contained modules or applications that can be independently developed, tested, and deployed. How they relate to microservices: Decoupling: Just like microservices, micro-frontends break down the application into smaller, independently deployable components. Technology Independence: Different micro-frontends can use different technologies (e.g., React, Angular, Vue) or versions of the same technology, allowing teams to work independently. Autonomous Teams: Frontend teams can work independently on specific parts of the UI without impacting the entire application. Example: A shopping website could have separate micro-frontends for product listing, checkout, and user profile, all developed and deployed independently.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: longside a primary service (microservice). The sidecar provides auxiliary functionalities like monitoring, logging, configuration, and service discovery without changing the core business logic of the primary service.

Real-world example (ShopNest)

ShopNest splits Catalog, Cart, Order, and Payment into services so teams can deploy catalog changes without redeploying payments.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.

Short answer: The Sidecar pattern is an architectural pattern where a helper service (the "sidecar") runs alongside a primary service (microservice).

Explain a bit more

The sidecar provides auxiliary functionalities like monitoring, logging, configuration, and service discovery without changing the core business logic of the primary service. Role of Sidecar: Decoupling: It decouples auxiliary functions (e.g., monitoring, security) from the primary microservice, ensuring that microservices focus on business logic. Reusability: Sidecars can be reused across multiple services (e.g., a logging sidecar can be attached to every service). Observability: Sidecars handle traffic-related concerns like load balancing, tracing, and logging, often integrated with service meshes. Example: Envoy is commonly used as a sidecar proxy for microservices to handle service discovery, monitoring, and routing.

Say this in the interview

1. Define — one clear sentence (the short answer above).
2. Example — relate it to a project like ShopNest or your real work.
3. Trade-off — when you would not use it.