In phase one of the catalyst, we successfully demonstrated the use of the AsyncAPI standards for event driven architectures as an alternative to the existing OpenAPI REST based definition. The TMF have now adopted AsyncAPI and a version of TMF 925 Async Trouble ticket is available on their site in the pre-production table. In this second phase of the catalyst we want to build on the work to create a real-world scenario using the ODA Canvas to show a use case that can use both AsyncAPI and OpenAPI as service providers will not be building all new systems and most likely evolve towards an event driven architecture and leverage their existing components as that happens. We will use a gateway that acts as an event bridge that provides an implementation of the TMF 688 event management API that allows components to create and register for topics over which event notifications can be sent. The topics can be sent either over OpenAPI REST call backs or to Kafka topics using AsyncAPI. The gateway will allow a company’s partners to use OpenAPI REST calls but does not require them to adopt new technologies, while allowing a company to transform its stack using a mix of existing components and new components built on Kafka or other such technologies. The component will be made available to members in the ODA Canvas as part of the catalyst, but the Oryx gateway requires a licence to use. We will submit a document that is a set of guidelines and recommendations on how to implement Async API using the TMF Event Management API which we hope will become an official TMF document.
BT Champion's statement
Async API Guidelines and Standards Proposal
Catalyst overview animation
Async API Catalyst Presentation
There’s finally a clear route to adopting EDA without architectural overhaul
Email the members of the Catalyst team to request more details.
GenAI hyper-personalized customer experience can increase lifetime value by up to 35%, revenue by up to 24% and reduce churn by 20%
With annual revenue of digital transformation reaching $20 billion, China Telecom is serving 10 million customers in 15 verticals.<br>
Build a new full-stack cloud native architecture to meet the cloud business needs of operators.