Trust Centre ยท Reliability
Keep the public path light. Keep the important path controlled.
Reliability in this category mostly means one thing: surviving everyone arriving at once. Here is how Beaver is designed for it, and what we have not yet evidenced.
-
Edge delivery
Live
Cached storefront HTML at the CDN edge, with live counters updating separately.
-
An isolated critical path
Live
Checkout is the transactional path; browsing does not queue behind it.
-
Process isolation
Live
Operators run in their own process pools.
-
Unattended jobs
Live
Draws and cart release every minute, journeys every five minutes, profile work hourly, rebilling nightly.
-
Monitoring with context
Live
Errors carry the operator that produced them.
-
Nightly offsite backup
Live
The database leaves the primary environment every night.
Numbers
No uptime percentage. No restore guarantee. Yet.
We will not publish "99.99%" without a status history, or a "15 minute recovery" without a documented and tested recovery process. A public status page is specced; when it exists it will live here.
- We will publish the number when we have earned the number.
