TM Forum Community

 View Only
  • 1.  Notification Listeners/Events in API

    Posted Jun 30, 2022 15:05
    Hi All,

    Why do we have different notification listeners/events end points in TMF open APIs ? Why not to map all events(create/update/delete) to one end point as all of them has same request body and refer to same data object and get the state change via path parameter?
    Referring to TMF 651 Agreement Management API.


    Charu Batra
    BT Group plc

  • 2.  RE: Notification Listeners/Events in API

    TM Forum Member
    Posted Jul 01, 2022 09:04
    Hi Charu
    The Open API event paradigm supports two distinct patterns:
    • The older hub-based pattern, where each API implementation is responsible for its own publish-subscribe capability
    • The Event API TMF688, which is a general-purpose technical API allowing wrapping of message and event buses such as Kafka, Rabbit, etc.
    You are free to use either, whichever makes more sense for your business and technical capabilities.
    Hope it helps

    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.