March 28, 2019 at 9:04 pm
Comments posted to this topic are about the item Trunk Based Database Development
March 29, 2019 at 2:18 am
Trunk based development works well when the deliverable is small incremental pieces of work delivered frequently. A rigorous set of mechanical tests is also essential.
It works well with stateless systems.
My experience is that it can work with much of what my team has to do with databases but there is a small but significant portion of changes where it doesn't. Typically when changes are made to tables that hold a significant amount of data or are accessed frequently. It isn't a case of one size fits all, it's a case of understanding when one is more appropriate than the other and reaching a common consensus as to when each should be applied.
March 29, 2019 at 10:56 am
I think it works when you also have either a very young system, where it's smaller and everyone knows how it works, or with a very old system that gets relatively few changes, or at least, from few people that can coordinate offline. It seems that in most corporate environments where teams don't talk, it's a recipe for disaster.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply