A microservices project separates independently managed services around clear responsibilities. It also introduces network failures, data ownership and operational complexity.
Before you begin
Be comfortable with variables, conditions, loops and basic methods. Use a small local project with a recorded JDK version and keep the input data fictional.
Work through the idea
Write the expected behavior before implementing the exercise. Keep the first version small enough to trace manually, then change one input or requirement. Record both the successful path and an invalid or empty-input case so that the result demonstrates reasoning rather than a copied output.
- Define service boundaries
- Assign data ownership
- Plan tracing and contract tests
Practice task
Design a fictional ordering system and compare it with a modular monolith.
Check your result
Explain one reason for separation and one cost, including failure between services.
A mistake to avoid
Do not split every database table into a service automatically.
Keep a review note
Save the inputs or scenario, your reasoning and the result you checked. Explain one assumption and one case that needs more work. Revise the exercise after feedback and distinguish what you demonstrated from what remains untested.
Official reference for further study
Explore the related learning path · Choose another worksheet