Currently as part of TMF Open API implementation in REST specification, we are developing each of those specification and TMF 668 is one of them
We had a question regarding the notification flow. In the design/spec document we have seen about the hub register flow and publish notification flow. However there was no info on when those notification is created.
Example let's assume that whenever new Partnership is created then subscribers in the hub needs to be informed about new Partnership which has been created.
What we have done is that when the new partnership is created, we are creating a new event entity with event type = create partnership and event body as the snapshot of the newly created partnership.
The event is then dispatched to messaging queue system ( Kafka,ActiveMQ) to process notification in asynchronously way.
The JMS listener then listen to the event and query the registered subscribers from the hub repository and publish the message to the consumer who are registered for those type of notification.
We could like to know if the approach taken is correct one ?? or do we have any reference architecture for implementation of notification flow use case ?
Also do we need to persist the notification message generated for any fallout scenario in case ?
The reference diagram created by us is attached, could you please check with any available analyst and let us know comment on the same ?Attached is high level design which we are trying to implement for integrating the PartnershipType entity and Event entity.
Let me know if there is any reference architecture artifacts which can be referred.Regards,Sanu