Another curiosity about (Spotify) Golden Paths. Sorry for having so many questions 😅. I perceive that the happy path is 1 golden path (e.g to deploy a Java/Go/whatever microservice in K8s) per repository. But, in case that a microservice needs to apply a schema change, is this part of the same golden path, or do you consider that is a different service that needs to be coordinated in the same flow?

I would say it is the same golden path (if the assumption that schema migrations are common for your organization is true). How you facilitate this golden path is up to you. (I would incorporate it in CI/CD pipelines. But I’ve also seen schema change execution on service startup. As long as you can automate the process, it would be great for facilitating the golden path (this also includes accounting for when and how to roll back (or have a solid only roll forward policy)).) Also, I don’t perceive the golden path as a happy path. More as a common path which you want to make easier for others to stay on.

Thanks @Joram Visser!

I’ve done schema changes on startup, depending on what you’re using you can usually have stuff that only runs on one instance of you app.

https://platformengin-b0m7058.slack.com/archives/C037XDKEDNW/p1652887535761699?thread_ts=1652879323.381759&cid=C037XDKEDNW this is likely a good idea in any case as otherwise rolling releases (the k8s default for deployments) will be difficult and rollbacks likely impossible.

did someone say schema change?? 🙂 pretty much all of us at Liquibase would be happy to talk to anyone about this at any time!

We are experimenting with init containers, is it good way to go ?

It still means you are taking out pod(s) from the rotation and I've personally found init container failures hard to debug.