The Good and the Bad of Serverless Architecture
If you’ve chosen to read this article, you’re likely aware that serverless computing is the next big thing in the cloud paradigm. In the last few years, around the time Amazon Web Services introduced its Lambda platform, serverless has become mainstream and buzzword-worthy with brands like BBC, Airbnb, Netflix, Nike, and many more adopters of the new approach to handle their back-end efforts.
Let’s begin by saying that the word serverless does not represent the actual state of the technology. There’s still a server somewhere; you just don’t need to buy, manage, or maintain it anymore. You outsource all server management to someone else, adding a level of abstraction in your cloud infrastructure. For developers, it means an ability to finally push server provisioning backstage and an overall friendlier way to create applications. For businesses – faster time to market and an idea of focusing on the what and why of deployment, instead of the how. Basically, the serverless approach is business-driven, the means by which third parties handle your technical concerns while you focus on delivering results.
Now, you may think, “We already keep our infrastructure in the cloud and don’t own any hardware. So, how is this different?”
Using a traditional cloud model (often called Cloud 1.0), you simply move your storage and networking to the cloud, but you still have to access and monitor it remotely via virtual machines (VMs). The serverless approach takes it to another level. Here, a programmer chooses an environment in which the code is written (Node.js. Python, C#, etc.) and uploads the code file which is then automatically deployed by the system. By using a vendor’s own ecosystem, you can easily describe how these services communicate and where they can access data. This is a near NoOps approach where most of the Ops is outsourced to a vendor.
How application deployment has evolved with cloud
For a deeper understanding of how it works, and what benefits it brings, let’s first describe some of the defining characteristics of serverless architecture.
Another name for serverless computing is Function-as-a-Service (FaaS), referring to the way developers assemble code into building blocks called functions. This is very similar to microservices where a large code monolith is split into small, manageable elements that can be scaled and updated separately and parallelly. However, FaaS takes it to the next level by breaking up the monolith even further.
Microservices vs serverless: same concept, different implementation
You obviously don’t want your home security camera to record everything that happens on your street 24/7. That’s why we use motion activated cameras to detect suspicious behavior when we’re not at home. Serverless architecture works similarly: Just like a motion sensor, it only works when a particular pre-programmed event is triggered. Serverless is stateless, meaning it only executes a task and doesn’t store or re-use requests.
The serverless approach is flexible and ideal for scaling applications. A FaaS vendor takes each of your functions and runs them in separate containers. This allows you to scale them endlessly and automatically. This is another difference between serverless and traditional cloud – here you don’t have to purchase the assumed amount of resources; you can be as flexible as possible. To make sure the travel management platform 4site can flexibly grow, we used AWS Lambda for the server(less) side of the project.
Billing per invocation
In a traditional cloud model, you need your servers to be ready to process requests at all times. Constant server availability leads to significant back-end costs every month, irrespective of CPU time and memory that are actually used. It’s like leaving your heater on all year long, regardless of the weather or change of seasons, and paying huge sums for unneeded electricity. Alternatively, serverless vendors allow you to pay a fraction of a price per request, which means that your costs will depend only on how much traffic you had this month.
Function-as-a-Service vendors such as Amazon Web Services Lambda, Microsoft Azure Functions, Google Cloud Functions, and IBM Bluemix OpenWhisk provide similar opportunities. When it comes to pricing, they’re all easy on the budget: up to one million requests are free, giving you a great starting point. The difference lies mostly in the community support and the availability of supported languages, which makes the choice rather personal. To figure out what is better for you, check our comparison of the major serverless providers.
What’s the big deal: pros of serverless computing
Engineering-wise, the benefits of serverless are obvious. It’s a simplified approach to development that eliminates a complicated layer, streamlining engineering efforts. But what about the business side of things? How do you persuade stakeholders that FaaS is the way to go?
⊕ Cheaper than the traditional cloud
As we mentioned, FaaS allows you to pay a fraction of the price per request. If you’re a startup, you can build an MVP nearly for free and ease into the market without dealing with huge bills for minimum traffic.
Everyone wants to build the next Uber, but would you risk provisioning infrastructure just in case? With serverless, you don’t have to make a choice, but you’ll still be ready for any volume of growth.
⊕ Lower human resources costs
Just as you don’t have to spend hundreds or thousands of dollars on hardware, you can stop paying engineers for maintaining it. That’s exactly how co-founders of productivity app Moo.do managed to deliver a product with their team of two.
⊕ Ability to focus on user experience
Abstraction from servers allows companies to dedicate more time and resources to developing and improving customer-facing features.
What to keep in mind: cons of serverless computing
Θ Vendor lock-in
When you give a vendor the reins to control your operations, you have to play by their rules. It’s also not easy to port your application to Azure if you’ve already set it up on Lambda. The same concern refers to coding languages: Right now only Node.js and Python developers have the freedom to choose between existing serverless options.
Θ Learning curve
Despite the comprehensive documentation and community resources, you may soon find out that the learning curve for FaaS tools is pretty steep. Also, to painlessly migrate to serverless, you might want to split your monolith into microservices, another complicated task to tackle. That’s why it’s preferable to get help from professionals experienced in serverless tools.
Θ Unsuitable for long term tasks
Lambda gives you five minutes to execute a task and if it takes longer, you’ll have to call another function. Serverless is great for short real-time or near-real-time processes like sending out emails. But long duration operations such as uploading video files would require additional FaaS functions or be better with “server-ful” architecture.
Serverless architecture use cases
Currently, most of the technology adopters are startups who seek for a possibility to scale painlessly and lower the entrance barrier. Serverless is also a perfect approach for applications that don’t run continuously but rather have quiet periods and peaks of traffic.
Internet of Things applications
The real-time response nature of the serverless approach works great for IoT use cases. Motion activated cameras that we’ve already mentioned, along with applications that react to changes in weather, temperature, or health conditions are perfect for the serverless paradigm that won’t allow your services to sit idle 24/7.
Virtual assistants and chatbots
People using chats expect immediate responses which is why serverless data processing can be faster. As your application grows from one hundred to several thousand users, your processing time should also stay the same which is automated with FaaS.
To maintain great user experience, developers have to provide multiple versions of the same images for different screen sizes – from desktops, to tablets and smartphones. This significantly decreases loading time. However, the tooling from AWS and Google will automatically optimize your images for any needs, making it a perfect solution for image-heavy applications.
Agile and Continuous Integration pipelines
The idea of running the code only when a certain event is triggered is perfectly in line with Agile or Continuous Integration principles. Separating your codebase into functions also helps with bug fixing and shipping updates. Serverless is an overall friendly way for maximum automation and rapid deployment processes.
Is serverless the future?
Going serverless doesn’t just mean a technical change but also a mindset change. For many companies running on legacy infrastructure, the migration will be painful and not as cost-effective as it’s promised to be for starting organizations. When you already have an established workflow, adopting FaaS tools to completely get rid of servers to manage is hard to justify. Plus, serverless is far from mainstream, though it’s moving in that direction and pretty fast.
In its Hype Cycle for Emerging Technologies 2017, Gartner predicts that serverless/FaaS will reach its plateau of productivity in 2-5 years, along with machine learning, VR and IoT. The technology is already available. The real struggle here is to determine the breadth of possible use cases and waiting for the larger language and functionality pool from all vendors.
This post is a part of our “The Good and the Bad” series. For more information about the pros and cons of the most popular technologies, see the other articles from the series:
The Good and The Bad of Xamarin Mobile Development
The Good and the Bad of Node.js Web App Development
The Good and the Bad of ReactJS and React Native
The Good and the Bads of Swift Programming Language
The Good and the Bad of Angular Development