Interview Q&A

Short answer: Add context to logs by including metadata like request IDs, user IDs, service names, and correlation IDs to trace requests across different services.

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 consistency across distributed databases can be difficult. Mitigation: Use eventual consistency, CQRS, and saga patterns to manage distributed transactions.

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: Gradually roll out changes to a small subset of users and monitor for issues. Once the deployment is validated, gradually increase traffic to the new version.

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: Use master-slave replication or multi-master replication to ensure high availability and load balancing for databases.

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: Record every change as an immutable event (e.g., using Kafka), allowing the state to be reconstructed by replaying events.

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: Automatically adjusts CPU and memory limits for the pods to optimize performance.

Explain a bit more

This is useful when pods experience resource contention but might not need horizontal scaling. Relevance to microservices: Kubernetes auto-scaling is essential in microservices to ensure that each service can scale independently based on its needs, without manual intervention. This allows the system to remain performant and available even as load fluctuates.

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: Automatically retrying failed operations a limited number of times can help mitigate transient issues. Use with caution to avoid overloading failing services.

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: Scaling Up: This involves increasing the resources (CPU, memory) for a specific microservice instance.

Explain a bit more

Vertical scaling is more common for monolithic applications or services that require more powerful hardware but is less optimal for microservices due to their distributed nature. Example: Increasing the memory or CPU for a service like the Payment Service that requires more processing power. Best practice: For microservices, horizontal scaling is preferred because it increases resilience and fault tolerance by distributing traffic and workloads across multiple instances.

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: URLs, API keys, etc.) in environment variables or configuration files.

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: pipelines and manage deployments.

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: Use tools like Prometheus and Grafana for monitoring metrics such as CPU, memory usage, request latency, and error rates. Implement distributed tracing using Jaeger or Zipkin to track requests as they travel across multiple services.

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: clusters of Docker engines and provides features for scaling, load balancing, and service discovery. In microservices, orchestration is crucial to managing complex systems and scaling individual services as needed. Example: Kubernetes can automatically scale the Inventory Service when traffic increases and roll out updates to the Payment Service without downtime.

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: Use Canary Deployments or Blue/Green Deployments to safely roll out changes.

Explain a bit more

These methods allow you to deploy new versions gradually and roll back easily if issues arise. If a rollback is required, it can be as simple as redeploying the previous stable version using container images or deployment configurations stored in a versioned system. Example: If the Order Service is updated to a new version and a bug is detected, you can use Kubernetes or Docker to quickly roll back to the previous stable version of the container.

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: Kubernetes Pods: Group one or more containers (microservices) into a Pod for management.

Explain a bit more

Deployment: Define a Kubernetes Deployment resource to manage the lifecycle of microservices (like scaling, rolling updates). Service Discovery: Use Kubernetes Services to expose the microservices and manage internal communication. Scaling and Autoscaling: Use Kubernetes to automatically scale services based on traffic, ensuring that resources are efficiently utilized. Example: After containerizing a User Service using Docker, you would deploy it to a Kubernetes cluster using a Deployment and expose it with a Service for communication with other 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: schemas. Use tools like Flyway or Liquibase for automatic version control.

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: services, but there might be temporary inconsistencies.

Real-world example (ShopNest)

After payment succeeds, ShopNest publishes OrderPaid. Inventory and Notification services react independently—no giant distributed transaction.

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: transactions, each handled by an individual service. Sagas manage failures by using compensating actions, thus avoiding the need for distributed locking.

Real-world example (ShopNest)

After payment succeeds, ShopNest publishes OrderPaid. Inventory and Notification services react independently—no giant distributed transaction.

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: local state based on received events.

Real-world example (ShopNest)

After payment succeeds, ShopNest publishes OrderPaid. Inventory and Notification services react independently—no giant distributed transaction.

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: eventually be consistent, even though there might be temporary inconsistencies. To manage consistency:

Real-world example (ShopNest)

After payment succeeds, ShopNest publishes OrderPaid. Inventory and Notification services react independently—no giant distributed transaction.

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: endpoints and enforce access controls.

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: in responses, and specify which domains are allowed to access the resources.

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 enforces role-based or attribute-based access control to determine if the user has permission to access specific resources.

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: claims (e.g., roles, permissions). This token is used to access microservices securely.

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: id=123&version=1 id=123&version=1 id=123&version=1 id=123&version=1 id=123&version=1 id=123&version=1 id=123&version=1 id=123&version=1

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: Responsibility Principle (SRP) in mind, meaning each microservice should expose only the functionality related to its domain. Avoid "fat" endpoints that do too much.

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.