Interview Q&A

The key elements of a resilient microservices architecture include:

What interviewers expect

• A clear definition tied to Microservices in Microservices projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microservices application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microservices architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

rchitecture?

n API Gateway is a server that acts as an entry point for all client requests to the backend

services in a microservices architecture. It acts as a reverse proxy, routing requests from

clients to the appropriate microservice, handling common concerns such as security,

logging, monitoring, and rate-limiting.

How it fits into microservices architecture:

• It abstracts the complexity of interacting with multiple services and provides a unified

interface to clients.

• It helps with centralized control of common concerns, improving scalability and

maintainability.

• It simplifies the client-side by consolidating multiple service endpoints into a single

entry point.

An API Gateway is a server that acts as an entry point for all client requests to the backend

services in a microservices architecture. It acts as a reverse proxy, routing requests from

clients to the appropriate microservice, handling common concerns such as security,

logging, monitoring, and rate-limiting.

How it fits into microservices architecture:

• It abstracts the complexity of interacting with multiple services and provides a unified

interface to clients.

Follow :

• It helps with centralized control of common concerns, improving scalability and

maintainability.

• It simplifies the client-side by consolidating multiple service endpoints into a single

entry point.

uthorization using an API Gateway?

Rate Limiting:

• Use the API Gateway to limit the number of requests a client can make in a given

period to prevent abuse and overload. This can be done using libraries or built-in

functionality in the gateway (e.g., NGINX, Kong).

• Example: Limit each client to 100 requests per minute.

uthentication:

• The API Gateway can integrate with external identity providers (e.g., OAuth 2.0,

JWT) to authenticate requests. It verifies the client's identity before forwarding

requests to the microservices.

• Example: If a request includes a valid JWT token, the gateway passes it

long; otherwise, it responds with an authentication error.

uthorization:

• The API Gateway can handle Role-Based Access Control (RBAC) by verifying

user roles from the authentication token (JWT) and enforcing access restrictions

based on the user's privileges.

• Example: Only admins can access /admin endpoints, while regular users

can access /user endpoints.

Rate Limiting:

• Use the API Gateway to limit the number of requests a client can make in a given

period to prevent abuse and overload. This can be done using libraries or built-in

functionality in the gateway (e.g., NGINX, Kong).

• Example: Limit each client to 100 requests per minute.

Authentication:

• The API Gateway can integrate with external identity providers (e.g., OAuth 2.0,

JWT) to authenticate requests. It verifies the client's identity before forwarding

requests to the microservices.

• Example: If a request includes a valid JWT token, the gateway passes it

along; otherwise, it responds with an authentication error.

Authorization:

• The API Gateway can handle Role-Based Access Control (RBAC) by verifying

user roles from the authentication token (JWT) and enforcing access restrictions

based on the user's privileges.

• Example: Only admins can access /admin endpoints, while regular users

can access /user endpoints.

PI Gateway?

Routing:

• The API Gateway routes incoming requests to the appropriate microservice based on

the URL, method, or other attributes. It can also aggregate responses from multiple

services and return a unified response.

• Example: Requests to /user are routed to the User Service, and /order to

the Order Service.

Load Balancing:

• The API Gateway often integrates with a load balancer to distribute requests across

multiple instances of a service, ensuring better resource utilization and failover

support.

• Example: Requests to a microservice like User Service can be distributed

mong several instances based on a round-robin or least-connections

strategy.

Caching:

• API Gateways can cache responses for repeated requests, reducing the load on

backend services and improving response times for frequently accessed data.

• Example: Cache responses to user profiles for 1 minute to avoid querying the

User Service on every request.

Follow :

Routing:

• The API Gateway routes incoming requests to the appropriate microservice based on

the URL, method, or other attributes. It can also aggregate responses from multiple

services and return a unified response.

• Example: Requests to /user are routed to the User Service, and /order to

the Order Service.

Load Balancing:

• The API Gateway often integrates with a load balancer to distribute requests across

multiple instances of a service, ensuring better resource utilization and failover

support.

• Example: Requests to a microservice like User Service can be distributed

among several instances based on a round-robin or least-connections

strategy.

Caching:

• API Gateways can cache responses for repeated requests, reducing the load on

backend services and improving response times for frequently accessed data.

• Example: Cache responses to user profiles for 1 minute to avoid querying the

User Service on every request.

Answer: PI versioning allows clients to continue using older versions of an API while enabling the introduction of new features. Implementation:

What interviewers expect

• A clear definition tied to Microservices in Microservices projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microservices application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microservices architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

like logging, monitoring, and security?

What interviewers expect

• A clear definition tied to Microservices in Microservices projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microservices application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microservices architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

Follow :

What interviewers expect

• A clear definition tied to Microservices in Microservices projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microservices application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microservices architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

spect API Gateway Service Mesh

Purpose Acts as a reverse proxy for

incoming client requests, routing

them to the appropriate service.

Handles internal

service-to-service

communication, including load

balancing, security, and

observability.

Scope Focuses on client-side requests

nd external communication.

Focuses on internal communication

between microservices.

Main

Responsibilitie

Routing, authentication,

rate-limiting, caching, logging.

Service discovery, traffic

management, observability, fault

tolerance.

Common Tools NGINX, Kong, API Gateway in

WS, Spring Cloud Gateway.

Istio, Linkerd, Consul, Kuma.

Integration 	Sits at the edge of the

rchitecture, acting as a

gateway between clients and

services.

Sits within the service mesh and

handles internal communications

between microservices.

Security Provides centralized

uthentication and

uthorization (OAuth, JWT).

Handles service-to-service

security using mutual TLS (mTLS)

for encrypted communication.

Use Cases External API access control,

cross-cutting concerns (e.g.,

rate limiting).

Service-to-service secure

communication, traffic control,

service discovery.

Microservices in Cloud and DevOps

performance, cost, and scalability in the cloud?

What interviewers expect

• A clear definition tied to Microservices in Microservices projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microservices application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microservices architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

ddresses. It simplifies service discovery by relying on existing DNS infrastructure and

ensuring that microservices can dynamically find each other without hardcoding addresses.

How it works:

• Service Registration: Each microservice registers its IP address and port with a

DNS resolver or service registry.

• Service Lookup: When a microservice needs to communicate with another, it

queries the DNS for the service's name (e.g.,

service-name.namespace.svc.cluster.local in Kubernetes), which returns

the corresponding IP address.

• Dynamic Updates: As new service instances are added or removed, DNS entries

re automatically updated.

Example: Kubernetes uses CoreDNS for service discovery, where each microservice gets a

DNS name that resolves to the service's IP.

DNS-based service discovery uses DNS records to resolve service names into IP

addresses. It simplifies service discovery by relying on existing DNS infrastructure and

ensuring that microservices can dynamically find each other without hardcoding addresses.

How it works:

• Service Registration: Each microservice registers its IP address and port with a

DNS resolver or service registry.

• Service Lookup: When a microservice needs to communicate with another, it

queries the DNS for the service's name (e.g.,

service-name.namespace.svc.cluster.local in Kubernetes), which returns

the corresponding IP address.

• Dynamic Updates: As new service instances are added or removed, DNS entries

are automatically updated.

Example: Kubernetes uses CoreDNS for service discovery, where each microservice gets a

DNS name that resolves to the service's IP.

In Kubernetes, service discovery is built into the platform:

What interviewers expect

• A clear definition tied to Microservices in Microservices projects
• Trade-offs (performance, maintainability, security, cost)
• When you would and would not use it in production

Real-world example

In a production Microservices application, teams apply this when handling user-facing features or integration boundaries. For example, you might use it during a sprint where reliability and observability matter—logging metrics, validating edge cases, and documenting the decision in an ADR so future developers understand why the approach was chosen.

How to explain in the interview

1. Define the concept in one or two sentences.
2. Context — where it fits in Microservices architecture.
3. Example — a specific project, bug, or performance win.
4. Trade-off — what you gain vs what you sacrifice.

Tip: Practice aloud on Toolliyo mock interview or the Interview Q&A section before your real interview.

A service registry is a centralized directory of available services and their instances. It

helps microservices locate and communicate with each other.

How it works:

• Each microservice registers itself with the service registry when it starts, providing

metadata like its IP address, port, and health status.

Follow :

• Other microservices query the registry to discover and connect to the required

service.

• Service registries also support health checks, ensuring that only healthy services

are discoverable.

Tools: Examples of service registries include Consul, Eureka, and Zookeeper.