The read path today
Five systems, one slow page
The product page needs attributes from the PIM, the entitled price from commerce, per-variant stock from the warehouse, the delivery promise from fulfilment and loyalty from CRM. That is five calls on the hot path.
Price after the button
The page waits for five systems, and when one is slow the price arrives after the button.
Six seconds at login
The account page takes six seconds to load because it waits for five systems.
Eight seconds on store wifi
The lookup takes eight seconds, so the colleague says I do not think we have it.
The filter disagrees
A filter promises in stock under 500, and the product page disagrees.
An empty slot
When one system is down the recommendations disappear, and the page looks broken.
Two tools, one slot
Two personalisation tools fight over the same slot, and nobody can say which one won.
Frontend teams build a backend-for-frontend to compose the response, and then own it forever. The person who wrote it leaves, and the team loses the knowledge of how it works. Reliability compounds downward: naive multi-source calls degrade from 92 to 44 per cent as sources go from one to ten. An AI data orchestration platform removes the code you own by moving composition off the hot path.
How it works
Composed before the request arrives
Enterspeed Core is an AI data orchestration platform that assembles facts up front instead of on the hot path.
- 1
Connect
Sync Connectors watch the PIM, commerce, fulfilment, CRM and search, detect changes and push them in.
- 2
Compose
Campaign & Entitlement Pricing resolves price per customer segment and campaign window. Context Graph filters, sorts and facets on the same shapes as the product page, and related product identities are materialised at write time so an outage cannot empty the recommendations slot.
- 3
Serve
The Delivery API serves one composed read: full attributes, the entitled price, per-variant stock and delivery promise, per market and per customer, fresh within seconds. Customer Context Cache holds orders, entitlements and loyalty in one read.
- 4
Hold
When a source is slow or down, the Delivery API serves the last known good state instead of failing the request. The page holds, stale rather than absent, and versioned contracts let a backend shape change without a frontend release.
Availability Truth tells the store colleague which warehouse has stock, and the lookup answers in under a second on store wifi. For organic and agent traffic there is server-rendered content with no client waterfall, real last-modified dates from change detection, Structured Data Projection so the markup and the page match, an Agent Trust Manifest stating which user-agents may read what, and an Agent Access Log recording who fetched what. Your PIM, commerce engine, fulfilment, CRM and search platforms stay authoritative.
Benchmark and reference
Published data, production stack
Performance data anyone can reproduce, and a European retailer running Enterspeed Core in production.
We measured server-side rendering performance across six JavaScript frameworks and published the method with the numbers, so anyone can run it again. The benchmark is vendor-neutral, and it is the kind of technical evidence a head of engineering can check rather than take on trust.
A European multi-market retailer moved off an IT monolith to MACH, using headless Umbraco, SAP, inRiver and Algolia, with Enterspeed Core orchestrating between them. A new commerce site plus an existing B2B site. No figures are published, and the customer is not named.
Ownership and lock-in
It replaces the BFF you maintain
The concern is that an AI data orchestration platform adds another dependency. It replaces one you already have.
The backend-for-frontend you own
- Frontend teams build a backend-for-frontend to compose the response
- The team owns that code forever
- The person who wrote it leaves, and the knowledge goes with them
- Every new channel is another fan-out to own
A managed composition service
- Enterspeed Core replaces the custom BFF and moves composition off the hot path
- Your PIM, commerce engine, fulfilment, CRM and search platforms remain the authoritative sources
- Versioned contracts mean a backend shape change does not require a frontend release
- When a source is down, the Delivery API serves the last known good state
Lock-in is a fair question. The composed data model is yours, the source systems stay authoritative and can be read directly if you choose to, exports are open, and adoption is non-invasive with no migration. There is no lock-in to one commerce suite, none to one model vendor, and a documented escrow process and exit path.
