The supporting cast

At 10:00 this morning, Case was not the only one watching a screen with a held breath.

In Traversal’s office, Finn has a wall of charts up: traffic arriving, entries landing, machines coping. That screen is an internal toolConcept · lights on your mapinternal toolSoftware built or configured for the people inside an organisation: support dashboards, refund panels, operations views. Full applications with frontends and backends and permissions, whose users happen to be employees., a full application in its own right whose entire audience is Traversal staff. Case will never see it, and it exists for mornings exactly like this one, when forty thousand strangers arrive at the same doors inside the same five minutes and somebody has to be able to tell, at a glance, whether the building is holding. Today it holds.

The companies inside the company

Two other names are awake and on duty, and neither is Traversal. Ledgerline will take the payments this morning. Semaphore will send the emails. Each is a third-party serviceConcept · lights on your mapthird-party serviceA capability provided by an outside company that a product connects to and uses: payments, email, maps, identity. Borrowed running capability, as distinct from borrowed code, gained at the price of depending on the provider.: an outside company doing, for money, a thing Traversal decided not to do itself. On purpose.

Deciding that is a whole discipline. To buyConcept · lights on your mapbuyUsing another company’s product or service instead of creating your own. You gain speed and their expertise, and you pay in fees, dependency, and reduced control. Buying shifts responsibilities without removing them. is to rent capability and accept the dependence. To buildConcept · lights on your mapbuildCreating and operating a capability internally. You gain control and pay for it in responsibility. Every specialised concern involved becomes permanently yours. is to own the machinery and every one of its problems. Dana, the product manager on Race Experience, asks the same question about everything, and the answers on the books are consistent. Payments were bought: moving money is a regulated speciality with someone else’s name on it. The timing ingest was built: it is the one thing Traversal must be better at than anyone alive.

The connection is work

Choosing Ledgerline was a decision. Being connected to Ledgerline is a construction. The credentials, the request formats, the error handling, the monitoring, all of it together is an integrationConcept · lights on your mapintegrationThe working connection built between separate systems so they can exchange information or capability. The API is what the provider offers; the integration is the connection your team constructs and maintains against it., and somebody at Traversal owns each one the way somebody owns a feature.

And every integration makes the other company a dependencyConcept · lights on your mapdependencySomething a system relies on in order to function: a package, a service, another team’s API. Dependencies have dependencies of their own, which is how an ordinary app comes to rely, indirectly, on hundreds of things.. If Ledgerline has a bad morning, Traversal has a bad morning too, contract or no contract, and nothing signed in a conference room last winter changes what happens to a Tuesday like this one. Finn’s wall of charts includes, for exactly this reason, one small chart that is really a question: how is Ledgerline feeling?

It is 10:01 and the answer, today, is fine. The race director, three boroughs away, is about to check something of their own.