This is a continuation from my last article on Running a Serverless Telegram Bot from AWS Lambda. Before that, I also wrote a simple guide to set up the basics, Send and Receive Messages with the Telegram API. This ties things together to finsh a working API.
ReadFunction as a service (FaaS) offerings are great for certain compute tasks. They are low maintenance, scalable, and cheap for infrequent workloads. Telegram bots can be used fairly infrequently, or might be constantly monitoring and moderating your chat with tens of thousands of users. The compute workload is quite variable, so if your chat is dead from 3am to 11am you won’t have to pay to keep a server running 24/7. On the other-hand, during a surge of activity, you won’t need to worry about running out of resources.
ReadTelegram is a modern cross-platform messaging app that I use frequently for group messages. Since I use it everyday and it has an open API, I thought it would be a convenient interface for some small project ideas I’ve had recently.
Read