Monolithic architecture packages and deploys an application as one unit. This can make a proof of concept easy to bundle and deliver, although the approach may create drawbacks as needs change. section 3.1
Choose a monolith by examining the project rather than following architectural fashion:
- Keep an existing monolith when it works; change it only after identifying architectural problems. section 3.1
- Consider team experience, project size, and risk factors before choosing between architectural approaches. section 3.9
- Treat microservices and containers as alternatives to evaluate when there is a demonstrated need, not as automatic improvements. section 3.1 section 3.9
A proof-of-concept application
A team can bundle and deploy a complete proof of concept as one package, then reconsider the architecture if concrete problems emerge during development or operation. section 3.1
