| Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events |
|
Hi,
I worked a bit on how to cope with failure scenarios. I put the ideas in a document that I share with you.
https://docs.google.com/document/d/1grD3MTq5056kyQnanZ7C8O_Rd0CXMJZ_aC1CL60DU0U/edit?usp=sharing
Cheers, Stefano From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Wednesday, July 26, 2017 8:23:25 PM To: kapua developer discussions Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events Hi all,
In the attached diagram I tried to give an overall view of the delete event-flow along with the services involved.
Cheers, Stefano
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Mehmet Arziman <mehmet@xxxxxxxxxx>
Sent: Wednesday, July 26, 2017 8:00:26 PM To: kapua developer discussions Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events Hi Jens,
I ve added some small inputs and points which came into my mind. I will try to add more to your proposal, soon.
I am thinking if we should (close after we know which technology could be feasable for service events) group and sort the service events that can be fly around in the system between services (system service events, business service events etc.).
Since this approach goes into a asynchronous event-based model, we should put a little time into this, if that makes sense. If not we can start with the already know service events and bring in the grouping or domains at a later time.
I will try to add more use cases the next days.
BR Mehmet
|