IT Glossary
What is Deployment?
Going live: the moment a new software version reaches the real servers and the real users.
Between "the code is finished" and "customers are using it" sits a step with its own name: deployment — installing the new version on production servers, with everything that entails: database migrations, configuration, post-release checks. It is the moment of maximum risk in software, where theory meets reality, which is exactly why a team's maturity can be read from what this moment looks like at their shop. The artisanal version: manual releases, rare, on Friday evening, executed from memory and adrenaline — one forgotten step means a site down all weekend. The professional version: automated releases through a CI/CD pipeline, frequent and boring — small changes, identical scripts every time, automatic verification afterward, and above all a rehearsed way back: rollback to yesterday's version within minutes if anything misbehaves. As a client evaluating a development vendor, two short questions separate the worlds: "how does a change reach production?" and "how long does it take you to return to the previous version?" Good answers sound like routine; answers that sound like heroism describe a cost you will eventually pay.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247
Why it matters for your business
Changes shipped without interruptions
Modern techniques — gradual rollout, switched servers — publish new versions without the site or app pausing for a second.
A guaranteed way back
A rehearsed rollback turns any bad release into a minutes-long incident — not a night of repairs under pressure.
Frequency reduces risk
Small, frequent releases have a small blast radius: if something breaks, the cause is in today's little change — not a quarter's backlog.
Frequently asked questions
Why do some deployments happen at night or on weekends?
For systems with service interruptions, the window with fewest users is chosen. Modern practice prefers the opposite: zero-downtime deployment during the day, with the full team awake at the controls — far safer than the Saturday-night release with half a person on call.
What is a rollback and why must one always exist?
The rapid return to the previous version when the new one misbehaves. It must exist because no amount of testing guarantees production perfectly; the difference between teams is not the absence of incidents but the minutes to recovery. Ask about the database too — the delicate part of any rollback.
What are test environments versus production?
Copies of the application where work happens safely: development (the construction site), staging (the dress rehearsal, as close to reality as possible) and production (the stage, with real customers). Changes flow through them in order — skipping stages is exactly what it sounds like.
Let’s talk about your project
Message us on WhatsApp or send an email — you talk directly to a developer.
office@northdan.com · +40 752 070 247