The most popular and comprehensive Open Source ECM platform
Code Development: The Serverless Use Case
Serverless computing is becoming increasingly popular but it’s not a one-fit approach for all applications. There are some use cases where serverless shines and others where it just doesn’t.
Serverless computing is often used in web and mobile applications, stream and batch processing, trigger-based tasks, the internet of things, REST APIs, cron jobs, and cloud automation.
Project characteristics that make a good fit for Serverless computing include:
- Stateless
- Application scalability
- Minimize server costs when there are frequent periods of low activity
Project characteristics that are not a good fit for Serverless computing include:
- Constant workload. Serverless works better in cases where the incoming frequency and volume fluctuates.
- Long-running functions.
- Stateful
- May not be easy to port from one cloud provider to another
Naina Singh, product manager at Red Hat, said that “a perfect use case for the serverless paradigm is for applications with non-uniform access characteristics with a spiky traffic shape. Serverless applications are also perfect for experimentation or exploring a startup idea, as the deployment costs directly correlate with usage numbers so that the investment risk is minimized.”