Covering Use Cases for a Serverless MVP
The following post is part of a series of articles chronicling my journey into serverless implementation via a sample Case Study using a minimal viable product (MVP). TL; DR the source code used for the implementation and instructions on how to run the app locally are on GitHub.
A Minimum Viable Product (MVP) for the Roku serverless screen saver application involves fulfilling two use cases.
1- Registering Users
Since the purpose of the case study is to only use resources on-demand there will be no traditional always-on website/server for users to register their accounts and start managing screen saver media. Users will use text messages to sign up for the service and also manage the images that are displayed on their screens.
The registration process will be secure so that only verified phone numbers can be used for accessing the system.
2- Managing Media
Users will be able to manage their screen saver images by sending text messages.
Workflow for saving media
Workflow for deleting media
.
