Serverless computing is a cloud computing execution model in which the the allocation of machine resources is dynamically managed. There is a good blog bost by Mike Roberts on serverless architectures for the interested reader. “Serverless computing” is misleading to some degree. Obviously servers are still needed, but the term “serverless” is used because the server management and capacity planning decisions are completely hidden from the developer or operator. Serverless code can be used in conjunction with code deployed in more traditional styles, such as microservices. However, applications can be written to be purely serverless as well.
There are very well curated link lists dealing with serverless computing in general like Awesome serverless. However, this blog post would like to concentrate only on the frameworks. The main intent is to curate a list of open source serverless frameworks over time. If you think some framework is missing do not hesitate to propose it.
Most public cloud service providers offer compute runtimes, also known as function as a service (FaaS) platforms. Here are some well known type representatives.
All of the mentioned commercial serverless computing models are prone to create vendor lock-in (to some degree). Therefore, open source serverless frameworks might be an alternative with the downside that the infrastructure must be operated. Obviously these frameworks need platforms or infrastructures to be executed on.
This list is likely not complete. If you know further serverless platforms do not hesitate to contact me.
While serverless platforms need infrastructures to be executed on, provider agnostic serverless frameworks provide a provider and platform agnostic way to define and deploy serverless code on various serverless platforms or commercial serverless services. This is an option to avoid (or reduce) vendor lock-in without the necessity to operate an own infrastructure.
This list is likely not complete. If you know further provider agnostic serverless frameworks do not hesitate to contact me.
Provider-specific serverless platforms are often optimized for operation from a provider point of view. But from a developper point of view there are a lot of opportunities to improve the task to develop and deploy serverless code in a more convenient way. The following frameworks make use of serverless infrastructures but provide more convenient (but still provider-specific) IDEs.
This list is not complete. If you know further provider-specific serverless frameworks and IDEs do not hesitate to contact me.