This post is part of a series on serverless computing with AWS Lambda, but is written as a standalone introduction to AWS Lambda with Java. In this post, I’ll create a very basic function which just echos back the message that I send to it. In the next part of this series, we’ll modify the function to do something a bit more useful!
JavaOne 2017 has been and gone and one thing that appeared on my radar this year was serverless computing. Not only because of a couple of announcements - Oracle have now launched their fn Project platform and Microsoft have announced support for Java in their Azure Functions platform - but also because of an interesting conversation I had with Ryan Cuprak. He, like me, has been working with AWS a lot and had been experimenting with AWS Lambda.
This post is, hopefully, going to be the first in a series of posts summarising some of the StackOverflow answers I’ve given in the past. I earned my first gold badge on the site this year - the “Unsung Hero” badge. What this effectively means is that I answer a lot of questions correctly and helpfully, but no-one cares.
As I write this blog post, on Tuesday 27th June 2017, I’m looking through memories of where I was on this day in 2016: participating in the keynote speech at Red Hat’s DevNation conference in San Francisco.
This is post is a long time coming. Not so long after I first joined C2B2, I had the job of making sure that our internal production servers were properly backed up. It was a pretty important job, but the sort where a young, new starter could be let loose without doing any damage, since the only real problem you can run into is accidentally taking too many backups. If you accidentally delete all the snapshots you’ve been taking to prevent that issue, well, you’re back where you started and nothing has really changed.