Backend Engineering
Microservices & Architecture
6 practice questions. Free questions open a full answer guide; the rest unlock with Pro.
- Your team is debating whether to pull a chunk of functionality out of the monolith into its own service. How do you decide where a service boundary should go, and when splitting is the wrong move?
- What are the main trade-offs between building an application as a single monolith versus splitting it into microservices?Go Pro
- You're splitting a monolith into services, and a checkout flow now spans an Orders service and a Payments service that no longer share a database. The team wants to keep the old behavior where the order and the charge either both succeed or both roll back. Walk me through how you'd preserve that guarantee across the service boundary.Go Pro
- Why is letting two microservices share the same database considered an anti-pattern, and what's the alternative?Go Pro
- A team wants to extract a new service from the monolith, but the proposed service still reads and writes several tables the monolith also owns directly. They argue it's faster to ship that way and split the database later. As the senior engineer reviewing the design, how do you respond?Go Pro
- In a microservices system, a single user action needs to update data owned by several different services. You can't wrap it in one database transaction. How do you keep the data consistent across those services?Go Pro
Want questions matched to your role? Paste a job title, job description, or CV for a personalized set, or go Pro to unlock the full bank.