Bots helped me understand Serverless Architectures / Services
Earlier in 2017, Serverless archies were one of the biggest innovations in the Cloud Computing, I’ve heard a lot about. But giving that I was a lot into bots, I just kept hearing without really dig into it.
A few months ago, I realized that I’ve been dealing with a real model of Serveless Archies 😮 😍
Serverless Architectures. Késako ?
Simply, Serverless is used for architectures and applications where the developer doesn’t need to bother about any infrastructure. The only concern is writing code and deliver it. We’re talking about Backend as a service or BaaS and code that’s executed in containers : Function as a Service or FaaS.
Serverless can also describe applications where we, developers, decide the server logic. Exept that, it is executed in stateless container triggered by events and managed by a third part application.
Most known example is : AWS Lambda which is an implementation of FaaS.
And bots ?
Serverless architectures are ideal for chatbots development. At the end, we’re developing event-oriented API that is capable of responding to a large number of requests. On the other hand, it is necessary to use SSL encyption on endpoints : webhooks for messaging services.
That means, we can use either Heroku, AWS, Microsoft Azure, Google Cloud or else, they are possible providers. What matters is what we develop a logic that will behave as a chatbot. Then we can deploy to any of these providers and make it respond to any messaging platform (Facebook Messenger, Telegram, Slack …) by configuring our webhook API according to the channel.
Using Serverless architectures and services is very beneficial because it avoids the waste of supply of machines and allows the ‘pay-per-use’.
