Difference between rolling, rolling with additional batch and immutable deployments in AWS?

Question

I am using elastic beanstalk to handle my deployments. I read the explanation for these deployment options but it was not quite clear. Could someone explain it in more simpler

Answer 1

I found this post easier to understand than the accepted answer, so here's my take on it.

Ordered by high-to-low risk, and calling the deployed versions v1 to v2:

• All at once: Replace all v1 with v2 at the same time. Failure not handled.
• Canary: A v2 is deployed and observed. If successful, all remaining v2 instances are deployed immediately.
• Rolling: Replace v1 instances with v2 instances one at a time. Watch for failures.
• Rolling with batch: Create some new v2 instances. If successful, roll out on v1 instances. When all are v2 instances, scale back to original size.
• Immutable: Don't change v1 instances. Create same number of v2 instances. Wait for success, then stop v1 instances.
• Blue/green: Instead of operating on an environment in-place, create a new environment (network, etc.) fully provisioned with v2, and switch over when ready.