Open APIs

 View Only
  • 1.  API Notifications - why its designed with endpoint address communication

    TM Forum Member
    Posted Dec 15, 2021 07:28
    Hi Experts.

    I know the event notifications model is discussed and designed accordingly.  I would like know the history regarding why the event notifications are designed with registering the communication endpoint address and not the messaging model (not like topic with publisher and subscription model).

    In this synchronous event notifications model, how the event producer API will ensure the reliability/guarantee of the event to consumer API?

    What if the consumer service is down for some time and the producer API tried for sending event?

    ------------------------------
    Thanks
    Santhosh Thatipally
    Oracle Corporation
    ------------------------------


  • 2.  RE: API Notifications - why its designed with endpoint address communication

    TM Forum Member
    Posted Dec 15, 2021 09:32
    For this eventuality, the Open API introduced more recently an Event API TMF688 (accessible here), which is intended to wrap durable message buses.
    You are probably right that point-to-point messaging needs more work, the notifier (message producer) needs to handle retries, etc. Having said that, even when working against a message bus it is possible that the bus is down and you'll need to retry, but it's easier to manage, presumably in one place.

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------



  • 3.  RE: API Notifications - why its designed with endpoint address communication

    TM Forum Member
    Posted Dec 16, 2021 03:51
    Thank You Jonathan.  Yes, there will be a problem in messaging when the message bus is down.  I will go over the 688 once and come back if any help needed

    ------------------------------
    Thanks,
    Santhosh Thatipally
    Oracle Corporation
    ------------------------------



  • 4.  RE: API Notifications - why its designed with endpoint address communication

    TM Forum Member
    Posted Dec 17, 2021 11:29
    Hi Santosh,

    The event notification model is not intended to be synchronous from application A to application B.
    The hub API is an interface to manage subscriptions of a publish subscribe pattern.

    It is the intention of TM Forum that implementers can implement this as wrapper around a message bus.

    My company offers a TMF688 application that takes away the hassle of creating your own implementation.
    It is build on the basis a cluster of Kafka brokers that can provide long term storage of notifications.

    For each subscription we create an independent caller thread that handles synchronous delivery to consumer applications.

    Conceptually producers and consumers can come and go. The resilient Kafka infrastructure should provide an always available message bus.

    Best Regards




    ------------------------------
    Koen Peeters
    OryxGateway
    ------------------------------