Microservices Anti-Patterns — Concept Check
Questions on Microservices Anti-Patterns. Common pitfalls include distributed monolith (tight coupling), chatty services, shared databases, synchronous call chains, and under-invested observability infrastructure.
Questions in this quiz
7 questions on Microservices Anti-Patterns — Concept Check. Work through them here, then start the quiz to answer them and see your score.
1.Your team notices that deployments are taking longer and require coordination across multiple services. Each service accesses a common database schema. What anti-pattern does this indicate?
- ASynchronous Call Chains
- BChatty Services
- CNano-Services
- DDistributed Monolith
2.A service operation requires calling multiple other services in sequence, resulting in high latency and failure rates. What is the primary anti-pattern here?
- AShared Database
- BNano-Services
- CSynchronous Call Chains
- DChatty Services
3.A microservice requires multiple round trips to gather data for a single operation, causing performance issues. What is the likely cause?
- ASynchronous Call Chains
- BDistributed Monolith
- CChatty Services
- DNano-Services
4.Your team is considering splitting a small service into even smaller ones to improve modularity. What should you be cautious of?
- ACreating Nano-Services that add overhead without benefit
- BReducing latency through smaller services
- CImproving observability
- DEnhancing team ownership by splitting services
5.A service is slow, but without centralized logs or distributed tracing, it's hard to diagnose. What is lacking in your infrastructure?
- AObservability
- BSynchronous Call Chains
- CNano-Services
- DProper API Gateway
6.Your team finds that multiple services are directly querying the same database tables. What problem does this create?
- AImproved scalability
- BFaster data access
- CHidden coupling and risky schema changes
- DReduced latency
7.What is a key indicator that a service might be a Nano-Service?
- AIt has multiple endpoints and a large codebase
- BIt improves system observability
- CIt requires a dedicated team for management
- DIt cannot be independently developed, deployed, and scaled