5 ms·

Hi. We open sourced our feature flagging product https://github.com/BulletTrainHQ https://github.com/BulletTrainHQ not long ago and would love any feedback from

Hi. We open sourced our feature flagging product https://github.com/BulletTrainHQ https://github.com/BulletTrainHQ not long ago and would love any feedback from HN. I still have concerns with deploying production upgrades behind flags due to the inherent issues surrounding things like database schema mismatches, terraform/infra upgrades that are not compatible bidirectionally etc. Has anyone worked on ways to manage these with feature flags?

loopz 6y ago
It is possible but you need to design versioning in message and storage schemas from the start. It's a non-trivial thing, but can be done. I'm not aware of any general solution available, so need a bespoken design effort. You need to map out requirements for versioning beforehand, and the complexity and future limitations will follow exactly from requirements. If instead of converging to versioning, you want full-on branching that never merge, this sounds like very chaotic design. You'd then maybe want to design everything around feature isolation (see: UNIX philosophy), but comes with own caveats around new requirements and cross-cutting concerns.