Avoid API Chaos: L'Oreal's Proven Governance Model
summary
L'Oréal adopts API‑first and a data strategy in 2020 and builds a Center of Enablement to enforce ownership and standardize naming across 18 data domains, cutting duplicate attributes and improving data quality. The platform stack uses Google Cloud for data, Confluent/Kafka for EDA and a gateway/portal assembled with Drupal and automation to publish APIs from a Gravity API Designer export into Apigee via ServiceNow automated forms. They track adoption with dashboards and a four‑axis quality review—compliancy, security, maintainability, sustainability—and run documentation and rating features to drive reuse.
AI-written summary · about
chapters (12)
- 0:00L'Oreal's API governance intro
- 1:10Team structure & API platform
- 2:33Data strategy & APIs
- 4:00Data ownership & standards
- 7:13API types & governance
- 9:50API product owner roles
- 10:33Training for API owners
- 11:41API lifecycle tools
- 13:27API performance tracking
- 14:54API docs & reuse challenges
- 16:16Monitoring API quality
- 17:40Conclusion & future
related talks
43mAPIs, a game changer for the personal care industry.
26mAPI Governance as a fundamental pillar of the Renault transformation
26mWhy Your API Governance Fails at the Operating Model
56mWhat are the means to accelerate the API strategy
24mSelecting the best API Governance for your organization
40mAutomated Governance in Practice
23mAn Operating Model for API Platforms
32mThe 7 commandments for a successful API Program