Monthly Archives - October 2025

Magento Upgrade

Worried about Magento major version upgrade risk and downtime?

Customers have some basic requirement

  • During go live have a very short downtime.
  • Give me a way to rollback when there is a problem in the upgrade

Here is a blueprint that we follow.

  • Create a parallel environment for new staging and new prod
  • Make sure code is deployed using CI/CD
  • Make sure staging is tested often by taking a live db backup
  • Do a dry run before actual go live
  • For reducing downtime use a mysql read-only replica strategy. During go-live (or dry run) simply promote the database and run setup upgrade (with keep-generated) flag

Magento merchants – let us declare freedom from codefreeze. Deploy-at-will.

This holiday season, Magento merchants - let us declare freedom from codefreeze. Deploy-at-will.

It is 2025 and this is not an unreasonable expectation. No more code freeze before the holiday season. Heck, changes are needed right during a sale. A UI update, a new marketing plugin integration.

Before you get that freedom, you need to ensure you take are of this small list.

  • A staging environment "12factor app" similar to prod. (Same software versions and connections, same code, similar db). Ensure you deploy to staging before you deploy to prod.
  • A horizontally scalable architecture. Does not need to autoscale, but atleast on demand add and remove CPU. No more "make it large" before the sale as you really don’t know what is large.
  • CI/CD with true 0-downtime deployment - along with rollback.

If you don’t have these, good luck.
Or, you can move to luroConnect and enjoy a holiday season like it should be - lots of sales, lots of fun, none of the headaches that pull you away from your family.