Description
What this service covers
If you still schedule releases for 2am on a quiet Sunday, this project ends that routine. A new version starts up and must pass health checks before any traffic reaches it, while the previous version stays running so you can switch back instantly. Database changes follow an expand-and-contract pattern, so old and new code can run side by side during a release. We rehearse the full process in staging, including a release that is broken on purpose.
What you receive
- Blue-green or rolling deploys set up for your virtual machines or managed container platform
- Health check endpoints built and tuned to your application’s real startup behaviour
- Load balancer target groups and connection draining configured
- Expand-and-contract database change pattern written up and applied to one live release
- Automatic rollback if health checks fail within a defined window
- Release runbook, including the manual override steps
- Failure drill rehearsed with your engineers observing
The work in 4 stages
-
01
Stage 1: Current-state mapping
We trace today’s deploy steps, the causes of downtime and how tightly the database is coupled.
-
02
Stage 2: Groundwork
We build health checks, the schema change pattern and the needed infrastructure updates.
-
03
Stage 3: Staging rehearsal
We release in staging, then force a failure to show rollback works.
-
04
Stage 4: First live release
The first production release is carried out together with your team.
Who it suits, and what we need from you
Ideal for
- Products with users across several time zones
- Teams paying a regular price for late-night releases
- Businesses with uptime obligations written into customer contracts
What we need from you
- Access to the application code and the environment it deploys to
- Part-time input from a developer who understands the database schema
- A staging setup that is reasonably close to production
You share these through the brief on your order page after checkout.
What changes for your team
- Releases happen during working hours with the team available
- A faulty release is reversed in minutes without restoring the database
- Deployments become everyday work, not a planned event
Questions about this service
Will this work with just one database?
What if our app is slow to start up?
Could we use canary releases instead?
This is a remote service: nothing is shipped physically, and the work is delivered into systems you control. See delivery and handover and refunds and cancellation for the full terms.
Reviews
There are no reviews yet.