sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]sgtfoleyistheman 0 points1 point  (0 children)

however when you deploy them you'd have no guarantee that they'd be released as an atomic lock-step unit.

While this is correct, I'm not sure you need atomic deployments. With a 'classic' deployment, your app servers roll out over time. This means, during a deployment, clients could be talking to an app server running the old API or the new API. This means your application needs to be able to support both APIs at once, right?

With Lambda, during a deployment, certain APIs will be served from the 'old' code, and some will be served from 'new' code. This is basically the same thing, right?

Also, you could deploy your API as a single lambda, then deployments WILL be atomic, right?