A toolkit for deploying and operating serverless architectures on any platform. Makes it much easier to create and deploy functions. Postlight also has a starter kit based on Serverless, adding Webpack, Babel, ESLint, and Prettier. Serverless Stack is a complete step-by-step course you can take using a note-taking app as a demo.
Deploy Node.js projects to AWS Lambda and API Gateway easily.
A curated list of awesome services, solutions and resources for serverless / nobackend applications.
This Medium publication has a whole section on serverless with loads of articles. A couple of recent notable ones being How we migrated our startup to serverless by Ivan Montiel and How serverless reduced our costs by 70% by Mohsiur Rahman.
An overview of its history, basic concepts, providers, frameworks, benefits and drawbacks.
Serverless opens up tons of possibilities for what you can build right on CodePen! Let's dig into this and build ourselves a fully functional blog.
A tutorial on building a ToDo app with React where the data is stored in Firebase connected to a Redux Store.
The thread which ties them together is getting communities of sites to work together across domains, but powered by the front end.
2017 is shaping up to be the year of serverless computing, most notably through AWS Lambda and Google Cloud Functions created through Firebase.
A video series on how to use Firebase to set up a Web Push Notifications feature from client-side to server-side.
How to seamlessly add realtime features to your polling app using Pusher while visualizing the data on a chart using CanvasJS.
Build a serverless URL shortener using Amazon Web Services (AWS) Lambda and S3.
In this four-part tutorial, we’ll go over how to set up a serverless function, make it talk to the Stripe API, and connect it to a checkout form that is setup as a Vue application.
Should your EC2 be a Lambda? How much would you save by going serverless? Which of your applications can harness event-driven architecture, blazing-fast deployment, incredible scalability, and decreased cost of AWS Lambda?
Calculating cost for AWS Lambda, Azure Functions, Google Cloud Functions, and IBM OpenWhisk.
Explore the benefits of GraphQL over REST, and build a feature rich webshop using Graphcool and the Serverless Framework.
Build a serverless e-commerce app using AWS Lambda, Stripe and React ensuring your website is ready for traffic peaks.
Architechture diagrams of serverless architectures
In this tutorial, we will build a serverless payment application with Stripe and AWS Lambda.
Outlines the pros and cons of Express and Serverless and explains why it made sense for our team at Pilcro to switchover. This piece is aimed at tech teams looking to deploy and manage Node.js APIs on AWS (or similar).
I have discovered, AWS Lambda and the Serverless Framework make it really not that hard to deploy an application.
What if I told you that you could build a Static Site Generator with your own custom CMS without the need for a database?
The serverless computing concept is an up-and-coming execution model that tries to address the needs of modern, cloud-based software.
How we set up the globe by making use of a Serverless function that gets geolocation data from Google for all of our speaking locations. I'll also run through how we're going to use Vuex to store all of this data and output it to the table and globe, and how we'll use computed properties in Vue to make sorting through that table super performant.
Learn the basics of Amazon Web Services (AWS) Lambda and Simple Email Service (SES) APIs to help you build your own static site mailer on the Serverless Framework.
Serverless computing lets developers deploy applications to the cloud without having to provision or manage a server—or pay for a server when it's not in use. How to develop serverless code with Apache OpenWhisk, an open source serverless platform. You'll also get an introduction to OpenWhisk with Bluemix.
Community driven podcast.
FaaS (functions as a service) is a paradigm shift in cloud – we've moved from real servers (physical, data centers) to fake servers (virtualization, containers, etc.) to uploading code and allowing a provider to run it in response to events. Something is quite different there. It is, of course, not possible without the previous innovations and strides, but a shift nonetheless.
We’ve created a simple internal platform that allows nanoservices to be uploaded, as code. It then allows a nanoservice to be executed on demand, via a RESTful API. There are no containers or servers dedicated to each nanoservice; instead, they all run on a shared platform. Which for us is a set of auto-scaling cloud instances.
But what is Serverless, and why is (or isn't) it worth considering? In this article I hope to enlighten you a little on these questions.
Discover how to migrate an API of an existing app to Azure Functions. You'll learn how to use Visual Studio Code and the Azure Functions extension to speed up your work.
Explore different use cases for building microservices with Serverless technology. The talk will include real world serverless examples from companies & the open source world.
.arc is a plaintext manifest for defining next generation cloud infrastructure
Get a REST API up and running quickly with the Serverless Framework by using a starter/boilerplate project called the Serverless Starter.
Are there still servers involved? Of course, but you don't manage them, scale them, or pay for them when you aren't using them. It really is a different model that deserves a new name.
Take some baby steps into building things with Serverless. We'll mostly be looking at cloud functions here and how using them from an otherwise static hosting environment means you've unlocked all sorts of possibilities.
While the content can be published to Firebase using its excellent CLI, a better approach is to have it fully automated. For doing this, first I set up a private repository on GitLab and make it as the remote origin for my local working repository.
Create a basic web application that uploads an image to an Amazon Web Services S3 bucket which will trigger an AWS Lambda function that will create several thumbnail images at different sizes. Once the images have been created, they'll be put into a different S3 bucket and rendered! We'll be using the Serverless framework to easily setup, manage, and deploy our AWS resources and lambda function. We'll be using Vue on the front-end to build several components.
You can use things like localStorage or indexedDB to store data. But that data is only for the one person looking at your creation, it's not data stored in some permanent database that persists across time and sessions and all that. Need that? There are plenty of options. Also see options for getting/setting JSON data.
I decided to build a tool of my own, but I didn't want to spin up VMs and configure expensive infrastructure to handle the load of a ton of redirects going through my servers. So, I decided to go serverless: the perfect task for Azure Functions to take on!
Walk through a simple example here of creating a StdLib service that responds to incoming messages. The end result will be fully customizable to support whatever SMS messaging functionality you require.
Go completely serverless by deploying Functions to Webtask and storing media files on Cloudinary.
Cloud apps are shifting into the serverless world and it will indeed bring about dramatic changes in how we create and distribute software and applications.
The latest face-off between Serverless vs Containerization. Contrary to the general belief, both of these technologies have good things in common.
Build a chatbot that's capable of extracting a text content from a picture (optionally translating it to different languages) and sending back the result to the user via SMS (or a phone call).
Who has time to babysit servers? Not me. I have code to write, and customers to keep happy. I could use just a static site generator like Jekyll, but we need more. I have important Internal customers - the marketing department. People that expect a nice web GUI for their CMS. How am I going to make that happen with a static website?
An 11-part workshop on using Webtask (and various other technologies) to build a Slack thingy.
Think about only using functions. No more managing servers. You only care about the code. Sounds rather cool. We as developers shouldn’t need to do the tedious work on the command line. Let the ops guys handle that. What do we even call this type of architecture? Only using functions? Small functions? Tiny services?