Microservices
Answer out loud or in your head first, then compare.
Answer
Microservices split a system into independently deployed services that own clearly defined business areas.
Benefits: independent deployments and scaling, clearer team ownership, the ability to isolate failures.
Costs: network communication can fail, requests are harder to trace, and data consistency and transactions across services need design. Add retries, idempotency, monitoring and contract versioning.
Example: separate payment and order services have to agree on what to do when the payment succeeds but the response is lost.
Pitfall: microservices aren't automatically better. For a small team a modular monolith can be simpler. Don't claim production experience you don't have.
How did it go? Be honest — “Not yet” puts the question on your review list.