Spent a month on this and I think I figured out how to get JSON to “roll over” a Step Function step that is a noop (no operation: function that doesn’t return a value), like say AWS Batch. Noop’s (no operation) are steps that basically are full of side effects, but really don’t have a useful return value beyond “SUCCESS”.Continue reading “Handling Noop Infrastructure in AWS Step Functions”
Friends have asked that I report a from the trenches update on my thoughts on Lambdas. I fell in love about a year ago, so how do I feel now? I’ll cover the pro’s and con’s I faced, what I learned, and what I still don’t know.
Continue reading “AWS Adventures: Part 3 – Post Mortem on Lambdas”
In the old days, you’d write code and allow another team called Operations (or OPs for short) to deploy it to various servers for testing, and eventually production. Quality Assurance teams would be testing your code from a few days to a few weeks ago on another server.
Developer tooling, infrastructure as a service, and shorter development cycles have changed all that. The Amazon practice of “you build it, you own it” has started to filter out to other companies as an adopted practice. Teams are now expected to build, deploy, and maintain their own software.
Today, I wanted to cover what I’ve learned about automated deployments around AWS. You’ll learn why you don’t need Ansible, Chef, or even Serverless, and instead can use AWS API’s to do everything you need.
At the beginning of October, I started a new project to help my team move a 12 year old application to the cloud. I knew next to nothing about Amazon, or their infrastructure offerings called AWS. In the past 3 months I’ve learned a ton. Today I wanted to share what I’ve learned about Lambdas: Functions you run in AWS.
Also known as serverless architecture.
Continue reading “AWS Adventures: Part 1 – Lambda”