Serverless UseCases.
some Use cases of serverless computing.
Batch processing an offline system, Batch processing takes a large amount of data at once and runs a bunch of jobs on it, In this scenario usually, the user will not wait for any sort of response back from the server, Jobs are scheduled and run in periodically Maybe we replace expanse on extract-transform-load(ETL)
Infrastructure automation IT-ops can automate scheduled jobs, monitor network changes, use triggers and events for verse different systems.
Stream processing an online/offline system, it is also called nearline processing. just like batch processing system, stream processing takes input and produces output. But stream processing works on events where batch processing. Stream processing builds upon batch jobs.
Today we use serverless managed services that process event streams since functions typically stateless in many platforms we can't do windowing and operations like that. There are great managed services for stream processing today in the cloud that require no infrastructure. No complexity.
3 - tier web apps or often SPA or sites that talk to serverless storage. Only invoked and run when someone uses it. a typical 3 tier web app
Web APIs are a great option, easy to build web api data and query systems and do simple calculations, release and deploy without setting up any infrastructure.
AI and machine learning Data crunching, just like stream and batch processing.
Further reading
Azure Serverless business senarios.
Amazon AWS step functions, lambda services
Google Cloud functions
summary
serverless functions are cheap and useful they have many use cases, Even though they are stateless and has a cold start time, The technology is still getting maturing at the time of this blog is published. Amazon is adding a lot of research on this area.