This is a list of design decisions to support the MVP of our product.
- We prioritize productivity and time to market, so we plan to use Rails since the team is familiar with the technology even if it might be suboptimal.
- Skip automated tests because of lack of time and money for the MVP
- We expect from 500-2000 active users using our systems daily. This should be easily achievable with a modest deployment in Google Cloud and Kubernetes.