Minimum Viable Architecture is a set of design principles which is very suitable for APIs, microservices and API management as it is designed for different stages of growth and maturity.
Use when building a new API
Use when building a new API for few consumers
Use when existing API has growing number of consumers
Minimum Viable API Architecture consists of Prototyping, Build Just Enough and Scaling -phase
Why is the MVA architecture chosen for this method
The MVA (Minimum Viable Architecture) approach is usable for any architecture design process.
Each Phase of MVAA goes through the entire APIOps Cycle. Development from here on goes in cycles and is iterative.
One of the key elements in Agile methodologies is Minimum Viable Product. MVP is a product with "just enough" features to satisfy early customers.
When they see and can try the MVP, they can give feedback for future development. Minimum Viable Architecture has a similar idea.
Designing architecture so they can be prototyped and built fast. The sooner the consumers get to use the API the faster you discover the real requirements.