InfoQ Homepage Continuous Architecture Series Content on InfoQ
Articles
RSS Feed-
/articles/minimum-viable-architecture-sample/en/smallimage/logo-1655129551476.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.
-
/articles/care-about-architecture/en/smallimage/logo-1652455760936.jpg)
Why You Should Care about Software Architecture
Software development teams have resisted "big upfront designs" in favor of architectural designs emerging from self-organizing teams, which can lead to a mindset that software architecture is not really that important. Greater awareness of the implicit decisions they are making, and forcing these decisions to be made explicitly, can help development teams make better, more informed decisions.
-
/articles/what-software-architecture/en/smallimage/logo-1649414695292.jpg)
Software Architecture: It Might Not Be What You Think It Is
Software architecture is often a misunderstood idea. Unlike traditional architecture, where the design is separated from construction, in software how something is built influences what is built, and vice versa. Software architecture is about decisions, not structure. Architecting is a skill, and architect should not be a role.