A short while ago, I wrote about how I converted my Ruby on Rails application over to a serverless
architecture reducing my need for running a server with a rails app,
relational database and so forth. Something I completely forgot about was the side worker I had implemented using
Sidekiq - a gem created to handle processing tasks. Given I was serving static content out of my S3 bucket, and the
processing was a lambda that would be fired each time a user ran, I didn’t think that it would…
One of the important considerations when running an application is knowing when there are errors, whether or not the
service is busy and understanding how your users are using the application to build the best user experiences and work
on delivering more business-value.
In the quest to move everything to a pay-what-you-use model and maintaining my enthusiasm for serverless, I was inspired
by Nathan’s post over on DevOpStar about
creating a chatbot using Facebook’s messenger platform. With my past as a town planner, I’ve been wanting to mix my two
skills with programming/devops and town planning to help make the community better for a while, but been struggling to
find some inspiration for an idea.