Q11. When should you not use microservices?
Avoid microservices when: - The domain is still being explored. Wrong boundaries are far more expensive to move than within a monolith. - The team is small. Each service ...
Technical Question Bank · Peer-Reviewed
Job Interview Questions and Answers Directory
Search and filter frequently asked interview questions across technical, programming, and behavioral domains. Tailor your interview preparation by difficulty for freshers or experienced developers (17 available).
Active:
Tag: service ×
Q12. What is an SLA and how do you work within one?
An SLA, or service level agreement, is a commitment about the level of service a customer can expect. It usually defines response times and resolution targets for differe...
Q13. What is a GCP service account key and why should you avoid it?
A service account key is a downloadable JSON file containing a private key that lets any holder authenticate as that service account. It is long-lived and does not expire...
Q14. Why does each microservice need its own database?
Owning its data is what makes a service independently deployable. With a shared database, a schema change in one service can break another, teams coordinate releases, and...
Q15. What is GraphQL federation and when do you need it?
Federation lets several teams own separate GraphQL subgraphs and compose them into one graph for clients. Each subgraph declares the entities it owns with a key directive...
Q16. How would you design a test strategy for a microservices system?
Testing a distributed system needs a layered strategy, because full end-to-end coverage does not scale. - Unit tests per service for domain logic, run on every commit. - ...
Q17. How would you design machine-to-machine authentication?
For service-to-service calls, avoid shared static credentials and long-lived secrets. - OAuth 2.0 client credentials: each service is a registered client with a client id...