I've told about why we started to explore serverless in my previous post. And this one will be about what we did and how it went so far. We used to have 9 servers (i.e., AWS EC2 instances) on multiple availability zones, each running a docker engine and all were interconnected with Rancher.

Throughout this series we have been exploring how to use serverless architectures to our advantage. In this article I will show you: How to create a serverless slack command using Node.js & Up, Best Practices when developing serverless applications, A curated list of serverless resources.

In Part 2: Serverless Scales I briefly touched on how a serverless architecture can have a cost benefit. In this post, I will go over: How to approach and analyze the cost of serverless, Two detailed examples of a cost analysis.

In Part 1: What is Serverless? I talked about how one of the biggest pros to a serverless architecture is how well it scales and how high availability is baked in. In this post I’ll go over: How a traditional highly available scalable architecture works, How a scalable serverless architecture works, How you can benefit from a serverless architecture.

In this post we’ll answer the following questions: What is serverless architecture? (and what it’s not), What are the pros & cons of serverless?

Function as a service (FaaS) products like AWS Lambda, Azure Functions, and Google Cloud Functions have instigated a paradigm shift in the way Ops teams provision and manage their organization's infrastructure. With everyday administrative tasks like provisioning, patching, maintaining compliance, and configuring operating systems all being abstracted away, your Ops team only has one task to work on - writing world-class code.

This small release introduces custom stages, stage-level configuration overrides, instant rollbacks and a few other refinements for Up the serverless deployment tool.

This is the first official release of Up Pro, which includes a number of improvements over the open-source version for production applications. If you’re unfamiliar with Up, it’s a tool which helps you manage and deploy serverless apis, apps and websites in seconds to your own AWS infrastructure. In short: it’s the easiest way to deploy Node.js, Golang, Python among others to AWS, and can cost as little as $1/mo to run or in some cases free.