Fire
Dev Track
FR
Lightning Talk

Map less, reference more: the alchemy of shared data

One list changes: how many systems do you have to fix?

Scène (lightning talks)
Presented by
Réserver ma place

How many identical lists of values exist in your information system today? One per department, probably. You know the pattern: new system, new list, start from scratch. Then you have to map it to all the others so the systems can understand each other.

It works. Until the day that list has to change. Then good luck finding every place it was copied, and making sure everything stays aligned.

We’d had enough. We built a single reference repository: values are managed in one place, exposed through an API, and propagated in real time to every consuming system via Kafka. No more mappings to maintain, no more copies to sync by hand, and the ability to organise these values into hierarchies to cover the most complex cases.

In this talk, I explain how the idea was born, how we put it in place, what broke along the way, and you leave with an architecture pattern you can apply directly to your own information system.

Dans le même parcours

See also