This post is part of a series on serverless computing with AWS Lambda, and follows on directly to the previous post on creating a basic AWS function. This post will assume you’ve read the previous one and modifies the code presented there.
This November I once again found myself in Antwerp at Devoxx Belgium. I’ve attended every one since we first launched Payara back in 2014! Over the years, I’ve been to quite a few conferences and I have to say that Devoxx Belgium is always my favourite. Stephan always finds a way to make each one unique!
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.