The two-day server

Somewhere in Traversal’s architecture is a piece of software that works two days a year and is a completely reasonable design.

The finisher-certificate generator renders a handsome PDF with a name and a time on it. It runs after Maple Grove and after Harborview, tens of thousands of times in two bursts, and then it does nothing at all for months. Renting it a permanent machine would mean paying for three hundred and sixty-three days of silence, and the ladder of alternatives is this scene.

The spectrum of who-runs-it

A self-managed serviceConcept · lights on your mapself-managed serviceA system the customer installs, patches, monitors, backs up and recovers themselves. Maximum control, and every unit of that control is also a responsibility. is the do-it-yourself end: your software on your instances, yours to patch at 2 a.m. A managed serviceConcept · lights on your mapmanaged serviceA system where the provider takes over the setup, maintenance, scaling, and recovery, for a premium and with less control. Build versus buy, applied to operations. moves the 2 a.m. work to the provider for a premium: the standby twin from Thursday is exactly this, a database whose failover machinery Traversal rents rather than builds. Act I’s build-or-buy question, asked again about operations instead of code, and answered the same way: buy the speciality, keep the differentiator.

And at the far end sits serverlessConcept · lights on your mapserverlessComputing where the customer supplies code and the provider runs it: no servers to provision or meet, billing per execution, scaling per event. The servers exist; you never meet them. Also called Function as a Service., where Traversal supplies only the code and the provider supplies everything else, invisibly, per execution. The certificate generator lives here. It costs nothing in the silent months, scales to the two loud days without a spreadsheet, and no one at Traversal has ever seen the machine it runs on. The name is a small lie, since the servers exist. Traversal just never has to meet them, and for software that works two days a year, never meeting the server is the entire point.

Sunday evening, the generator will wake, mint twenty-five thousand certificates including one reading 4:31:07, and go back to sleep for months. Next: the shelf the finished certificates, and everything else shapeless, actually sit on.