Even better, some documentation/article to build such a tool.
79 karma · joined June 9, 2016
Even better, some documentation/article to build such a tool.
Designing Distributed Systems https://www.oreilly.com/library/view/designing-distributed-s...
Building Evolutionary Architectures http://shop.oreilly.com/product/0636920080237.do
Building Microservices http://shop.oreilly.com/product/0636920033158.do
They encompass most of the topics you've enumerated earlier.
All my suggestions and ideas would just be dismissed as wrong and everything that person was doing would be right without explaining the why I was on the point of depression and got me thinking more than once about quitting my job but I liked the company too much.
It ended up with that person leaving. win-win.
The reason we use Flyway is that we are developing on the JVM so it has support for Java, Scala and Groovy (which we are currently using) and eventually also Kotlin.
I suggest to use a version control tool when you are in greenfield projects and your database schema and data might change a lot.
Additionally it offers an easy way to control and keep track on how the database evolves. Imagine having to run SQL statements directly on the production environment without a clear way of keeping track of the changes.
On top you will have consistent changes that you can roll-out across your dev, qa and prod environments in case you have that set-up.
As for how we run it, the migration scripts are part of the project and when we release a new version we apply the migration scripts automatically when the artefact bootstraps.
What time do they usually go to sleep and what is their noon daily pattern (weekday and weekends).
Most importantly how do they spend their time after 7pm during workdays and weekends ?