Great video! Thanks for sharing with the community!
@ElvisPapa89
Жыл бұрын
Really great video and very well explained all migration concepts! It would be really great if you can explain how to auto generate the DB schema change-sets when making a change into your schemas.
@pts0
2 жыл бұрын
Interesting video, thanks. I personally would challenge the point of view to allow release / versioning of application/service and data schema. If you are in control of application and data schema and have the possibility I would always make sure application and data schema are locked together and upgraded/migrated (rolled back) at same time. Keep it simple as possible, IT already have a lot of stuff that can go wrong ... Sure if you have multiple instances of services or no possibility of "one shot" upgrade with some downtime, you solution is the best. Maybe before going with independent release cycles/version of data schema and application you can challenge the design of the services/backend data schema. Why data schema is exposed to the service ? Are you not missing some abstraction layer between data layer, backend and exposed service ?
@OutOfDevOps
2 жыл бұрын
Hi Kim, thank you. I agree with you on keeping application code and database schema migration together, but the execution should happen in different releases. This way, you enforce best practices by design, developers cannot be tempted to bundle App and DB changes together (thinking: "well it's couple of seconds JUST the time to restart the service"). In addition it's very common to have multiple replicas of the same service and in many cases downtime is not an option (think payment systems). Keep it simple and do one thing at the time... and make it backward compatible as rollbacks in some cases (destructive operations on data) are not always possible. About your second question: > "Why data schema is exposed to the service ?" I am not sure I understand what you mean.
Пікірлер: 4