When I first heard the term Serverless, I just knew that this term had to be coined by either a salesperson or a marketing person. There are tons of servers involved in a cloud instance.
Serverless means provision as many or as few (even zero) servers on an as-needed basis. If there is no traffic, there is no cost and no servers in operation. Despite the misleading term, the concept of provisioning servers and server components - as-needed - is an ideal solution for large and small companies. So many benefits being serverless recounted in many articles.
What if your company is primarily an on-prem shop, and management doesn't understand serverless? Just the idea of not ordering a server, installing software, configuring the server on a network, and securing the server should thrill any IT department and non-executive, especially Finance. Not only that, the time saved in this whole process should be worth considering. Just imagine at any time, I can log into my Google console and - as they say - stand up a server in any flavor (Operating System) I want is pretty mind-blowing.
This concept shouldn't need much evangelism, but when old school culture collides with new school thinking - no matter the topic - there is bound to be resistance.
Serverless is the new thing because the advantages outweigh the disadvantages, but technology shifts back and forth like the wind. Though I don't see a future where servers are back on the premises, it still could happen.
At Notch, we will embrace the serverless model wholeheartedly. Watch this space as we chronicle our serverless journey.
The current serverless architecture configuration is for data exchange and event streaming utilizing Google Pub/Sub. A more in-depth discussion on how we use Pub/Sub in future articles.