One of the things this doesn’t solve is when your API is changing in concert with the Lambda function behind it. We need similar functionality in API Gateway to accomplish that. It’s also not “sticky”: a given client invoking the Lambda is, as far as I can tell, not any more likely to be routed the same way over multiple invocations (that’d be easier for a feature on API Gateway to do anyway, based on headers, etc.)

Cloud Robotics Research Scientist at @iRobot

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store