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.
Most of the applications I work on need continues almost real-time connectivity to data sources (either from a persistence layer or data emitting hardware). I was looking for opportunities to apply serverless architecture to learn more about the implementation and explore how/why serverless architecture is considered a viable option for next-gen uber like on-demand applications.
Since it is hard to convert/fit business applications to use newer paradigm without disruption, I have made up a case study that involves building a product (from design, development, DevOps, and publication) and set out to follow where the requirements take me and learn about serverless architecture in the process.
- Covering use cases for a serverless Minimum Viable Product (MVP)
- Serverless Architecture
- Serverless Business Layer
- Serverless Data Layer
- Presentation Layer
- Serverless Testing and DevOps
- Serverless Implementation Takeaways
The intended product:
Build and publish a Roku Channel app that displays screensaver of photos submitted via text message using serverless architecture.
Update: The MVP app is now published in the Roku channel store.