Capturing Solution Design Details In Serverless Developments — Part II
My previous article on the importance of Solution Design in serverless development discussed the need for it for the following main reasons.
- Technical agility
- Engineering clarity, and
- Business visibility
Nested among these is another one— Service Longevity. I often refer to this as the Sustainability of a serverless application (not to be confused with the new AWS Well-Architected Sustainability Pillar).
In a fast-paced agile environment, teams evolve, and engineers move around. Due to this, the domain and design knowledge fade from them. Storing the traces of what they went through, how they conceptualized the solution is vital. True, the source code repository plays its part, but it doesn’t explain the design unless captured and kept for everyone to understand.
This article introduces a documentation template to collate and keep the design details in one place.
Solution Design is a process of translating product requirements into architectural…
