Is there guidance on whether resources should only be created by direct calls to a POST api or whether events could be used for that purpose?Using 622 as an example1. Is the productOrderCreateEvent simply a notification that the productOrder resource has been created?2. Or can it be used as a directive, to trigger resource creation in an external system?Are we meant to look at the event and the api as interchangeable for certain operations (create, delete) on a resource or are there differences in semantics that are important to acknowledge?
The fact that some software listens to an ProductOrderCreate event (for example) doesn't mean that the software will now create a ProductOrder - it might be listening to the event for other purposes (e.g. to transform into a ServiceOrder for possible future provisioning).It does makes sense that a system listening to ProductOrderCreate event may create an internal resource in response. But using the service order example provides a slightly different use case in that there is a TMF spec for the service order. Is there any change to that pattern when there is TMF spec for the resource the other system will create?
Does SOM listen for the ProductOrderCreate event to trigger creation of it's service order (and leave it in a not started or waiting state) or does it expect that when a product order is ready to be provisioned, that the upstream system sends a POST /serviceOrder to SOM? I would have thought the latter but I suspect the answer is "whatever works for your organization based on who does the transformation" but I wonder what others are doing generally speaking for this downstream cascading of orders that have a TMF spec. We could imagine a layer below SOM than handles the resource order.Lynn