Experienced Devs

3981 readers

1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

Logo base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

snowe

jmk1ng

drewsiferr

Do your routine backend code releases require downtime? (lemm.ee)

submitted 1 year ago by [email protected] to c/experienced_devs

28 comments fedilink hide all child comments

Curious to know how many people do zero-downtime deployment of backend code and how many people regularly take their service down, even if very briefly, to roll out new code.

Zero-downtime deployment is valuable in some applications and a complete waste of effort in others, of course, but that doesn't mean people do it when they should and skip it when it's not useful.

you are viewing a single comment's thread
view the rest of the comments

[–] mrkite 0 points 1 year ago (2 children)

Our backend is written in Go... CI/CD compiles the binary, uploads it to the server under a temporary name, mv's it into place and -HUP's the process. So no downtime at all.

[–] austin 4 points 1 year ago (1 children)

what about after the HUP? The time between HUP and the new binary starting up would be considered downtime

[–] mrkite 1 points 1 year ago

We're talking milliseconds. The whole thing is run through an nginx proxy which would immediately retry if it failed.