> For the complete documentation index, see [llms.txt](https://amartyushov.gitbook.io/tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://amartyushov.gitbook.io/tech/app-aspects/software-architecture/app-dev-notes/architecture-mvp.md).

# Architecture MVP

{% hint style="info" %}
MVP is useful not only for business functionality to validate some hypothesis. MVP of architecture is useful to check your assumptions before jumping into complex and production-ready implementation.
{% endhint %}

Questions which should be addressed before/during arch MVP:

* Which hypothesis are you going to validate in scope of your MVP

Classify your risks before starting MVP:

* Resilience risks (fault tolerance). Отказоустойчивость.
  * e.g. what will happen if db is lost (Fix: think about backups)
  * can system recover after failure automatically 
* Performance risks
  * which bottlenecks appear at the rise of the load (Fix: caching, async)
  * Where some blocks/locking, or concurrency can occur
* Security risks
  * how safely your data is transferred and stored
* Scalability risks
* Tech stack choise risk