Monoliths and Microservices
What rule must hold even when someone bypasses the interface, repeats a request, or receives an external-service error? Prefer a well-structured monolith until independent scaling, ownership, or release needs justify distributed operations.
What You Will Be Able to Decide
- Explain monoliths and microservices in product and business terms.
- Apply this decision: Prefer a well-structured monolith until independent scaling, ownership, or release needs justify distributed operations.
- Recognise this material risk: service boundaries multiply deployment and failure complexity before the organisation can support them.
- Use this review: Trace one support request from submission to stored status, including a duplicate click and a provider timeout.
A founder is reviewing how the product will enforce rules and respond when a request does not go to plan. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
What rule must hold even when someone bypasses the interface, repeats a request, or receives an external-service error? The course example is A service that lets customers submit and track support requests; use it to decide what evidence would justify the choice before a builder implements it.
What Does Monoliths and Microservices Mean for Your Product?
A founder is reviewing how the product will enforce rules and respond when a request does not go to plan.
Use the illustrative service for this course (A service that lets customers submit and track support requests) to make the choice concrete. What rule must hold even when someone bypasses the interface, repeats a request, or receives an external-service error?
Technical term
Monoliths and Microservices
A monolith deploys product capabilities together, while microservices separate capabilities into independently operated services.
How Should a Founder Use Monoliths and Microservices?
For a service that lets customers submit and track support requests, ask what would happen if service boundaries multiply deployment and failure complexity before the organisation can support them.
For this decision, the useful standard is that important rules hold for valid, invalid, repeated, and unauthorised requests.
- Decision: Prefer a well-structured monolith until independent scaling, ownership, or release needs justify distributed operations.
- Evidence to request: show that important rules hold for valid, invalid, repeated, and unauthorised requests.
- Owner: name who will respond if service boundaries multiply deployment and failure complexity before the organisation can support them.
- Record the result in the backend proposal and operational acceptance criteria.
- Practical review: Trace one support request from submission to stored status, including a duplicate click and a provider timeout.
How Do You Choose an Approach to Monoliths and Microservices?
What rule must hold even when someone bypasses the interface, repeats a request, or receives an external-service error? Prefer a well-structured monolith until independent scaling, ownership, or release needs justify distributed operations.
The risk is that service boundaries multiply deployment and failure complexity before the organisation can support them. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Monoliths and Microservices?
What Warning Signs Should You Look For?
- The proposal does not address this risk: service boundaries multiply deployment and failure complexity before the organisation can support them.
- Nobody can show whether important rules hold for valid, invalid, repeated, and unauthorised requests.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to monoliths and microservices?
- How have we reduced or accepted this risk: service boundaries multiply deployment and failure complexity before the organisation can support them.
- Can you demonstrate that important rules hold for valid, invalid, repeated, and unauthorised requests?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Prefer a well-structured monolith until independent scaling, ownership, or release needs justify distributed operations. Ask for evidence against the specific risk: service boundaries multiply deployment and failure complexity before the organisation can support them.