Service 04 / 06
Delivery with a way back.
Automated delivery with checks that actually block, and a rollback that has already run once before the emergency.
When this fits
Four situations in which this service is the right answer.
- 01.1
Deployments no longer happen on Fridays, because nobody knows what will be broken on Monday.
- 01.2
The pipeline is green and production still goes down: the checks check the wrong thing.
- 01.3
The environment on one colleague's laptop is the only one where everything works.
- 01.4
An outage is reported by a customer, not by monitoring.
How I work
Order and stance. The four steps themselves are under Process.
A pipeline is only as good as the check that stops it. So the work starts at the gates: which tests, which security and licence checks, which build artefacts have to pass before anything ships, and what happens when they don't? A gate that can be bypassed will be bypassed sooner or later.
Environments are generated from code rather than maintained by hand. Development, preview and production differ only in configuration, which is what makes a clean run in preview say something about production.
Monitoring and alerting are aimed at the questions that matter in an outage: what is broken, since when, and how do we get back? The rollback is rehearsed before it is needed.
What you get
What belongs to you at the end and lives in your accounts.
- 03.1
A CI/CD pipeline as code, with gates for tests, security and build
- 03.2
Reproducible environments for development, preview and production
- 03.3
Monitoring, alerting and a documented, tested rollback
- 03.4
An operations runbook that genuinely helps in an emergency
When I advise against it
The cases where I advise against it, told to you before the engagement.
I do not build a pipeline that only I can operate afterwards. Your team has to be able to trigger a deploy on its own once I am gone, or the handover has not happened.
Questions
What is usually asked about this service.
01Which platforms do you work on?
Most often GitHub Actions, Docker and infrastructure as code on Cloudflare, Vercel or your own infrastructure. Existing platforms such as GitLab are no obstacle; the principles stay the same.
02We already have a pipeline. Is it still worth it?
Often, yes. Most pipelines ship reliably, but few really block. An assessment of the existing gates is a small, clearly bounded engagement, run remotely from Mainz wherever your team sits.
03How fast is a rollback?
It depends on the application. Minutes for stateless services, and for database changes as long as the migration takes backwards. Which is exactly why I plan and rehearse it beforehand.
Let's talk.
You get an honest first assessment — including the times I tell you not to do it.
- kontakt@navigaite.de
- Phone
- +49 156 79701573
- Response time
- The same working day.
- Privacy
- No cookies. No trackers. No banner.
- Location
- Mainz, DeutschlandMainz