Interview Q&A

nd what are the challenges?

Importance:

• Decoupling: Each microservice manages its own data, avoiding shared database

bottlenecks and promoting service independence.

• Scalability: Independent databases allow microservices to scale individually based

on load.

• Flexibility: Services can choose different types of databases (SQL, NoSQL) based

on their needs (e.g., relational data for one service, document store for another).

• Autonomy: Microservices can evolve independently without impacting others, as

database changes in one service don’t affect others.

Challenges:

• Data Consistency: Ensuring consistency across distributed databases is complex.

Eventual consistency and patterns like Sagas need to be used.

• Data Duplication: Some data might need to be duplicated across services, which

can lead to synchronization challenges.

• Complexity: Managing multiple databases increases operational complexity, such as

database migrations and monitoring.

Importance:

• Decoupling: Each microservice manages its own data, avoiding shared database

bottlenecks and promoting service independence.

• Scalability: Independent databases allow microservices to scale individually based

on load.

• Flexibility: Services can choose different types of databases (SQL, NoSQL) based

on their needs (e.g., relational data for one service, document store for another).

• Autonomy: Microservices can evolve independently without impacting others, as

database changes in one service don’t affect others.

Challenges:

• Data Consistency: Ensuring consistency across distributed databases is complex.

Eventual consistency and patterns like Sagas need to be used.

• Data Duplication: Some data might need to be duplicated across services, which

can lead to synchronization challenges.

• Complexity: Managing multiple databases increases operational complexity, such as

database migrations and monitoring.

cross multiple machines or instances.

When to implement:

• When you need to scale horizontally: When your database grows beyond the

capabilities of a single machine or instance, sharding helps distribute the load.

• High throughput requirements: Sharding allows you to handle higher traffic loads

by distributing the database across multiple servers.

• Geographical Distribution: If you have users spread across different regions,

sharding can help with distributing data closer to the users for performance and

latency reasons.

Considerations:

• Complexity: Sharding adds complexity in terms of data distribution, querying across

shards, and maintaining consistency.

• Balance: Shards need to be balanced to avoid uneven load on individual nodes.
• Cross-Shard Joins: Joins across shards are often difficult and can hurt

performance.

Follow :

Database sharding is the process of splitting a database into smaller, more manageable

pieces called shards, each of which holds a subset of the data. Shards can be distributed

across multiple machines or instances.

When to implement:

• When you need to scale horizontally: When your database grows beyond the

capabilities of a single machine or instance, sharding helps distribute the load.

• High throughput requirements: Sharding allows you to handle higher traffic loads

by distributing the database across multiple servers.

• Geographical Distribution: If you have users spread across different regions,

sharding can help with distributing data closer to the users for performance and

latency reasons.

Considerations:

• Complexity: Sharding adds complexity in terms of data distribution, querying across

shards, and maintaining consistency.

• Balance: Shards need to be balanced to avoid uneven load on individual nodes.
• Cross-Shard Joins: Joins across shards are often difficult and can hurt

performance.

Answer: Data synchronization across microservices can be achieved using a few key patterns:

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.

To implement eventual consistency in microservices with a distributed database:

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.

Advantages of Event Sourcing:

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.

Purpose: Service discovery helps microservices automatically discover and communicate

with each other, eliminating the need for hardcoded service addresses.

Implementation:

• DNS-based: Use DNS-based service discovery (e.g., Kubernetes DNS) to map

service names to IP addresses. This allows dynamic service discovery without

manual configuration.

• Service Registry: Tools like Consul, Eureka, or Zookeeper store service instances

in a central registry. Microservices query the registry to discover the location of other

services.

• Kubernetes: In Kubernetes, services and endpoints provide built-in service

discovery. Kubernetes automatically updates DNS records when pods or services are

created or removed.

Answer: In Kubernetes, load balancing is an integral part of service discovery and can be implemented in the following ways:

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.

Client-Side Load Balancing:

• In client-side load balancing, the client is responsible for selecting the appropriate

instance of a service to send the request to, based on the list of available instances.

• The client usually obtains the list of service instances through service discovery

(e.g., Consul, Eureka, Kubernetes DNS).

Pros:

• More control for the client on load balancing strategies (e.g., round-robin,

least connections).

• Reduces pressure on centralized load balancers.
• Cons:
• Adds complexity to client-side logic.
• Requires the client to maintain a list of available instances.

Server-Side Load Balancing:

• In server-side load balancing, a centralized load balancer (e.g., NGINX, HAProxy,

Kubernetes ingress controller) is responsible for distributing the traffic to available

service instances.

Pros:

• Simpler client-side logic.
• Centralized control over load balancing logic and configuration.
• Cons:
• Can introduce a bottleneck or single point of failure.
• Requires more resources and maintenance for the load balancer itself.

nd how do you overcome them? Challenges:

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?

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.

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

service.

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

re discoverable.

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

Answer: Sticky sessions (also known as session affinity) ensure that a user’s requests are consistently routed to the same instance of a service for the duration of a session.

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.

Answer: To handle service discovery across multiple regions or clouds, you need a global service registry or a service mesh that can span multiple regions.

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.

Answer: To secure communication between microservices, you can implement a combination of encryption, authentication, and authorization strategies:

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.

uthenticate each other using TLS certificates.

How it works:

• Server Authentication: The client verifies that it is communicating with the legitimate

server by checking the server's certificate.

• Client Authentication: The server also verifies that the client is legitimate by

checking the client's certificate.

Importance in Microservices:

Mutual TLS (mTLS) is an authentication protocol where both the client and server

authenticate each other using TLS certificates.

How it works:

• Server Authentication: The client verifies that it is communicating with the legitimate

server by checking the server's certificate.

• Client Authentication: The server also verifies that the client is legitimate by

checking the client's certificate.

Importance in Microservices:

user's data without exposing credentials.

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.

Answer: OAuth 2.0 is an open standard for authorization that enables third-party services to access a user's data without exposing credentials.

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.

Answer: n API Gateway serves as a reverse proxy that routes requests from clients to backend microservices, providing an essential layer of 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.

Answer: Role-Based Access Control (RBAC) assigns permissions based on the roles that users or services have within an application.

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.

Answer: Cross-Site Request Forgery (CSRF) is an attack where an attacker tricks the user into making a request to a service they are authenticated to, potentially causing unintended actions.

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.

uthorized, and encrypted. Key Principles:

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.

Answer: The Zero Trust Security model assumes that both internal and external networks are untrusted, and therefore, every request (internal or external) must be authenticated, authorized, and encrypted. Key Principles:

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.

(Distributed Denial of Service) attacks?

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.