Let the cloud providers handle everything else.
Believe it or not you can get infinite scaling, full security, and high performance for nearly zero operational cost. You should concentrate on building features that add value for your customers. And you can do that much faster when you don’t have to worry about anything else.
Red Badger built a customer portal for CarTrawler in 2 months. With multiple microservices that cost from $10 each a month to run. At scale. We used serverless architectures…
Use the cloud’s highest level of abstraction - Go Serverless!
Serverless doesn’t mean no servers, just that servers are no longer something we have to think about. Along with scalability and networking infrastructure. It’s really Functions-as-a-Service (FaaS) and simply amounts to providing code that we want to be run when an event such as a website visit, or some data from an IoT device, or a message from another application, happens.
Serverless is perfect for stateless transformations (i.e. take some data from somewhere, do something with it and send it somewhere else), and that’s a surprisingly large number of applications (including websites and APIs). Because scaling is extremely fast and handled by the provider, it’s also great for bursts of peak traffic and saves you the (still extremely challenging) tasks of having to set this up yourself.
Serverless encourages microservice architectures and allows us to concentrate on writing code that delivers value rather than worrying about orthogonal concerns such as scalability, security, and reliability. It’s also really, really cheap (you can invoke a function millions of times for a dollar!) largely because you don’t have pay for servers sitting idle.
Amazon is leading the way with its Lambda offering. Microsoft has Azure Functions in beta. Google Cloud Functions and Auth0 Webtasks are also competing. IBM’s OpenWhisk is open-source and may well become important for running serverless on-premise.
As serverless matures it is bound to become the defacto way that we run code in the cloud (and probably on-premise too).
Read more about the tech we love.