Hacker News Reader

Isn't this what rolling updates in container-based deployment systems (e.g., Kubernetes) do? And also the reason we have CI/CD pipelines and micro-services (to decouple processing from data).

So basically, in your example, change the code that handles GET and then trigger the CI/CD. Your code will be compiled, containerised then a rolling update is started to replace the old version of the running web server with the new one.

View on HN

What you're describing works great if the server is running at head.

I'd like the server to be able to execute a code path which mimics my Git branch, and on the next request to execute a code path which mimics your Git branch.

If you and I have two different versions of f(), I'd like them both to be available to be executed, based on some flag or condition.

As we merge our branches, f() will collapse back into the CI/CD pipeline you imagine, yes.

Reply on news.ycombinator.com