Skip to content
data & real-timenational publishing group

Live sports data, across several outlets.

A backend that collects sports data from an external feed and serves it in real time to a publishing group’s portals, each with its own style.

The project in numbers

A single backend
many outlets served
Customizable widgets
same source, the portal’s own style
Live events
traffic peaks across millions of users
the system, in cross-sectionfrom feed to portal
one source, three outputshow the same data wears three different looks

One backend, and every portal keeps its own identity.

The feed files are not consumed and thrown away: they stay. Parsing and the API work on top of them, and every outlet embeds the widgets in its own style without duplicating a line of code.

from source to backend
External FTP feed
the raw files stay, they are not consumed
a single backend
Cron parsing and archiveReal-time API
same data, three outfits
Outlet A
widgets in their own style, same API
Outlet B
widgets in their own style, same API
Outlet C
widgets in their own style, same API
noteThe outlets in the figure are generic: the number of portals served changes over time.
what changes

A single backend feeds different portals: the data is shared, the presentation is each outlet’s own.

And it holds through live-event peaks, when traffic multiplies in minutes.