InfoQ Homepage Minimum Viable Architecture Content on InfoQ
Articles
RSS Feed-
/articles/continous-architecture-article-series/en/smallimage/continuous-architecture-article-series-logo-small-1655735648162.jpg)
Article Series: Continuous Architecture
In this series of articles, the authors reframe software architecture in terms of decisions that teams make about how their system will handle its quality attribute requirements (QARs). In their view, software architecture, reframed in terms of decisions, completes the picture of how the system works by making clear the choices that the team has made, and why.
-
/articles/minimum-viable-architecture-sample/en/smallimage/minimum-viable-architecture-in-practice-small-image-1656333586692.jpg)
Minimum Viable Architecture in Practice: Creating a Home Insurance Chatbot
Even a simple application, like the one described in this article, needs a minimum viable product (MVP) and a minimum viable architecture (MVA). This is the second article in a series on MVA.
-
/articles/minimum-viable-architecture/en/smallimage/logo-1654507242099.jpg)
A Minimum Viable Product Needs a Minimum Viable Architecture
Creating a Minimum Viable Architecture as part of an MVP helps teams to evaluate the technical viability and to provide a stable foundation for the product that can be adapted as the product evolves.