[Event Technology]Modernization
Retiring a product module from a monolith without a risky delete
A module blocked at the web-server layer under a phased rollout plan, with a rollback path kept instead of deleting code.
- rollout
- Phased
- code deleted up front
- Zero
- path kept open
- Rollback
Context
The same enterprise event platform had a Venue Sourcing module that the business decided to deprecate. It lived deep inside the legacy monolith, next to features clients use every day.
Challenge
Deleting the module outright would touch many shared code paths at once, with no quick way back if something clients still relied on broke.
Approach
- Analyzed the impact of the deprecation across the monolith.
- Compared implementation options and presented them to stakeholders.
- Defined a phased rollout.
- Blocked access to the module with Apache rewrite rules instead of removing code.
Result
- A phased rollout, with the module blocked at the rewrite layer instead of deleted.
- A safe rollback path kept for the rollout.
Role & stack
Principal Software Engineer / Technical Lead · team of 30
- PHP Smarty
- Apache rewrite rules
- Amazon Aurora MySQL 8
- AWS
- Jenkins
- Bitbucket
- rollout
- Phased
- code deleted up front
- Zero
- path kept open
- Rollback
Role & stack
Principal Software Engineer / Technical Lead · team of 30
- PHP Smarty
- Apache rewrite rules
- Amazon Aurora MySQL 8
- AWS
- Jenkins
- Bitbucket
Architecture
