API Governance as an enabler of an architectural evolution The SNAM experience
summary
SNAM shifts a legacy gas-company IT estate from monoliths to microservices and claims the change cuts the main-application count by over 50%, uses Kafka for resilient data flows and wraps lifecycle control in AP Share plus identity and DevSecOps pipelines. The architecture supports a 41,000 km transmission network and nine storage sites, inventories previously scattered services, turns reusable microservices into productized APIs, and reports faster time-to-market, lower TCO and clearer partner integration through an emerging API marketplace.
AI-written summary · about
chapters (13)
- 0:00SNAM and API governance intro
- 1:29SNAM’s digital transformation
- 3:18Monoliths to microservices
- 5:06Unmanaged microservices challenges
- 7:34Need for API governance
- 9:01Microservices as digital products
- 10:29API governance with AP Share
- 12:15SNAM’s governance principles
- 14:05Governance beyond internal teams
- 16:07Governance with DevOps
- 17:13Bridging tech and people
- 18:36Lessons and benefits
- 20:03Conclusion and outlook
related talks
26mAPI Governance as a fundamental pillar of the Renault transformation
25mAPI Management - THE key differentiator in digital markets
29mEnhancing Governance, Cost Efficiency, and Developer Productivity.
26mAPIs as Agent of Change
25mTransforming the enterprise with APIs
29mAdapting to an API Enabled World (Panel Debate)
52mAPI Governance at Scale
23mLeverage APIs to Transform Your Business Landscape