|
Ithaqua posted:The other big challenge is to get people to start using feature flags and short-lived dev branches so you can ship your code even if a feature is half-completed. The killer is usually database stuff -- it's hard to get into the mindset of never (rarely) introducing breaking database schema changes. "Breaking" database schema changes can be part of a toggles/feature flags approach too, the key to making that easy is having an SOA architecture where you don't have 50 different apps reading and writing from the same database tables. If you instead have your tables behind a service that manages them, you can work around those changes within the bounded context and ensure you're not impacting anything used in production (e.g. if someone added a not-null column that's not used yet, you can have your service insert default values to that column for the time being) Of course, if you're refactoring the entire schema structure, your changes to the service itself are probably going to be too catastrophic to push that to prod either, not everything fits neatly behind a feature flag.
|
#
¿
Jul 6, 2015 17:48
|
|
|
|
| # ¿ May 4, 2024 12:35 |
|