Serverless logo

Serverless

The most widely-adopted toolkit for building serverless applications
2.2K
1.2K
+ 1
26

What is Serverless?

Build applications comprised of microservices that run in response to events, auto-scale for you, and only charge you when they run. This lowers the total cost of maintaining your apps, enabling you to build more logic, faster. The Framework uses new event-driven compute services, like AWS Lambda, Google CloudFunctions, and more.
Serverless is a tool in the Serverless / Task Processing category of a tech stack.
Serverless is an open source tool with 45.9K GitHub stars and 5.6K GitHub forks. Here’s a link to Serverless's open source repository on GitHub

Who uses Serverless?

Companies
353 companies reportedly use Serverless in their tech stacks, including HENNGE K.K., Primer, and Shelf.

Developers
701 developers on StackShare have stated that they use Serverless.

Serverless Integrations

AWS Lambda, Amazon API Gateway, Prisma, Azure Functions, and Prisma Cloud are some of the popular tools that integrate with Serverless. Here's a list of all 13 tools that integrate with Serverless.
Pros of Serverless
14
API integration
7
Supports cloud functions for Google, Azure, and IBM
3
Lower cost
1
Auto scale
1
Openwhisk
Decisions about Serverless

Here are some stack decisions, common use cases and reviews by companies and developers who chose Serverless in their tech stack.

Needs advice
on
AWS LambdaAWS LambdaClaudiaClaudia
and
ServerlessServerless

Which one is the best between Serverless framework and Claudia for AWS Lambda deployment? I just need the detailed difference between them to understand which is better.

See more
Joshua Dean Küpper
CEO at Scrayos UG (haftungsbeschränkt) · | 1 upvote · 118.4K views

As the basis of our new infrastructure, we formerly used CoreOS (and transitioned towards Fedora CoreOS as CoreOS was reaching its EOL) as a reliable solution for our docker-server-instances. We plan to deploy all our servers as individual docker containers to make use of the extensive possibilties offered in terms of isolation, resource-managemant (cgroups) and scalability.

The additional abstraction through containers allows us to adhere very closely to the "Cattle not Pets" best practice. Serverless was also an option that we considered, but as running Minecraft-Server requires quite unique resource profiles, that are usually not covered at most cloud providers, we settled with CoreOS for the time being and will reevaluate our options in the years to come.

See more
Praveen Mooli
Engineering Manager at Taylor and Francis · | 18 upvotes · 3.8M views

We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

To build #Webapps we decided to use Angular 2 with RxJS

#Devops - GitHub , Travis CI , Terraform , Docker , Serverless

See more

Serverless Alternatives & Comparisons

What are some alternatives to Serverless?
AWS Lambda
AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.
Terraform
With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.
Zappa
Zappa makes it super easy to deploy all Python WSGI applications on AWS Lambda + API Gateway. Think of it as "serverless" web hosting for your Python web apps. That means infinite scaling, zero downtime, zero maintenance - and at a fraction of the cost of your current deployments!
Kubernetes
Kubernetes is an open source orchestration system for Docker containers. It handles scheduling onto nodes in a compute cluster and actively manages workloads to ensure that their state matches the users declared intentions.
Azure Functions
Azure Functions is an event driven, compute-on-demand experience that extends the existing Azure application platform with capabilities to implement code triggered by events occurring in virtually any Azure or 3rd party service as well as on-premises systems.
See all alternatives

Serverless's Followers
1178 developers follow Serverless to keep up with related blogs and decisions.