Hey Joe, what is your specific use-case for canary deployment? Also, could you elaborate on what you mean by “plans for serverless “?

I finished watching the video about Datomic Ions and it has answered my question.

Basically by canary deployment, is it possible to do a rolling update in production? if something goes wrong then immediately revert to previously working production.

by Serverless I believe thats what the Lambda proxies solve. All in all Datomic Ions seems to answer my needs.

thank you for your answer Joe!

RE: canary deploy, It depends again on what you mean by “something goes wrong”. Right now, if you initiate a deployment and the ec2 instance fails to complete its code deploy steps, then the deployment is marked as failed and (in a production topology) there is zero downtime. Now, if the code deploy succeeds on a given instance and your code starts up but the latest release of your code is “too slow” as measured by a cloudwatch metric you have set up, datomic ions can’t fail the build on your behalf because it appears to have succeeded as far as Code deploy is concerned. Hope that clarifies things and I’m glad I could help.

okay thank you Joe!