What are the pros and cons of serverless?
Serverless is a development approach that replaces virtual machines with power that comes into existence when demanded, and disappears after it’s been used.
A cloud service provider is run by Google Cloud Platform, Azure or AWS, and you can configure events such as API requests or file uploads that trigger your serverless function to execute. When the action is completed, the server goes idle, which means you’re not paying for that time until another action is requested.
A serverless approach provides great opportunities to scale, as concurrent users can be accommodated straightaway, before being scaled back immediately when the traffic calms down, giving you increased performance of your app.
The serverless approach provides your infrastructure, manages capacity and avoids downtime, allowing you to spend less time managing servers and more time on the actual running of your business or organisation.
Through this reduced development time, your products can go to market faster as you’re not wasting time on the infrastructure of your app – it’s already sorted for you. As a disadvantage, with servers sitting idle when traffic is low or non-existent, there can be a lag in executing tasks.
If speed is mission critical to your organisation (for example, if you have a search or e-commerce website) this may not be the ideal solution for you. You’ll also not have much control over your server; your service provider will assign you storage and decide other specifications for you, which could be a hindrance if you have large image or video files to process.