Impacts: CSP’s CTO Architecture office

The challenge: TM Forum Open APIs enable interoperability and seamless end-to-end management of complex digital services through ODA & RESTful Open APIs. However, this might pose a challenge for CSPs with an architecture based purely on an event-driven architecture (EDA) paradigm. In this situation, the CSPs rely only on event streaming platforms, where the events’ production and consumption are typically done asynchronously, making them unable to leverage the out-of-the-box definitions of the TM Forum Open APIs.

Proposed solution: TM Forum Open APIs are based on the industry-standard Open API format to specify the RESTful contract. We want to leverage the same TM Forum Open API definitions but convert them into the relevant industry-standard for events-based systems (AsyncAPI). By doing so, we ensure that the underlying definitions, design patterns, schemes are being re-used in event-based interoperability.
We’d love to hear your perspective. Use the buttons on the left to tell us if you think this idea is important for the industry to address, or if you would like to get involved in working on a solution in a Catalyst project on this topic.
Or maybe you have an idea for addressing a different challenge. If so, submit your idea here.

Success measures: We aim to demonstrate, using a sub-set of the Open Digital Architecture use-cases (described in IG1228) (e.g., UC003, UC004, and UC007), how different components will be integrated using an event streaming platform (e.g., Kafka) where events are based on the TM Forum Open API schemes, and the AsyncAPI contract describes the contract, again leveraging the same operations from the TM Forum Open APIs.