Keep the focus on creating business value.

• What are Serverless Components?
• Why use Serverless Components?
• What are the benefits of Serverless Components?
• How to use Serverless Components?
• Serverless Framework vs Serverless Components (coming soon)

This article is part of a series of related articles which dive into serverless components, we hope you enjoy.

In this article we will look at why Serverless Components were created and why you should pay attention.

Why use Serverless Components?

First off if you haven’t read the article called, What are Serverless Components, please read that first.

Alright, let’s talk about how we got here. Back in 2015, Serverless Inc. created the Serverless Framework. A simplified way to define AWS CloudFormation and a godsend for those who were trying to build something called serverless applications.

Serverless application development, depending on who you ask, is a way of building applications which actively tries to put the focus and keep the focus on business value, above all else. Not on building infrastructure. Not on managing infrastructure. But, building the actual things that bring your business value. Crazy.

Read this article: Serverless is a State of Mind by Ben Kehoe

The Serverless Framework brought us closer to the idea of focusing on business value and over the past four years a lot has developed.

We’ve seen an explosion in open source contributions to the Serverless Framework and tons of people creating templates that others can leverage to move faster and focus less on recreating the wheel and more on the end product that brings us business value.

As of 11/16/2019 the Serverless Framework is at 32k stars on GitHub and growing.

The Serverless Inc. team seeing these trends develop introduced Serverless Components. A way to focus on your use case and help create an ecosystem that developers from around the world can tap into to build applications.

Yes, Serverless Components are new.

As of 11/16/2019 Serverless Components are at 1.4k stars on GitHub and the product offering by Serverless Inc. is still in beta.

However, it’s not hard to imagine a world in which every common and uncommon use case is defined as a Serverless component. Where a serverless developers job is to simply connect these components together and modify them with slight tweaks to encompass any edge cases or company specific requirements.

Imagine that world. Imagine if you as a developer or your development team weren’t spending 6+ hours debugging some small piece of YAML or JSON to make something deploy and work.

Imagine adding a handful of lines of YAML and seeing entire applications magically construct, deploy, and connect with only minor input.

Imagine what will happen when the focus is shifted away from the infrastructure as code and the focus is instead on improving every other aspect of your application.

‍