I'm with Iron.io, thanks for the mention. Interesting to see the architecture/patterns so front and center all of a sudden, it's what we've been doing for a whi

I'm with Iron.io, thanks for the mention. Interesting to see the architecture/patterns so front and center all of a sudden, it's what we've been doing for a while now. Very true that a key benefit of AWS Lambda is the ability to hook into the internals, but to the article's point, that's a pretty significant level of lock-in. We recommend to our customers who want a similar level of functionality hook up the internal events to SNS, at which point a job can be triggered on our end. We operate across any cloud, standardizing through Docker images as the unit of code. It's "serverless" to the developer in that the only configuration is setting the event triggers. Of course there's compute involved, but it's outside of the development lifecycle.