3 ms·
Have you seen that done in production? It sounds really dangerous, I've worked for an app server company for years and this is the first I've heard of this patt
by tinco 2y ago
Have you seen that done in production? It sounds really dangerous, I've worked for an app server company for years and this is the first I've heard of this pattern. I'd wave it away if I didn't notice in your bio that you co-created Django so you've probably seen your fair share of deployments.
- written-beyond 2y agoJust asking, isn't this what every serverless platform uses while it spins up an instance? Like it's why cold starts are a topic at all, or else the first few requests would just fail until the instance spun up to handle the request.
- tinco 2y agoYeah definitely. The dangerous part is having migrations or some other preparatory task be a part of it. When you're mixing concerns like that, you open yourself up to more complex failure cases and a larger surface area for bugs to arise. I feel that when you've grown to the size where zero downtime deploys are so important you'd do custom code just to enable them, it would be best to just invest in industry best practices and do backwards compatible deploys.
- simonw 2y agoI first heard about it from Braintree. https://simonwillison.net/2011/Jun/30/braintree/ https://simonwillison.net/2011/Jun/30/braintree/
- deleted 2y ago[deleted]