Hi all,
following the discussion and feedbacks of the last meeting (Tue 22nd) we introduced
some simplifications/changes to the EventStore proposal:
- Removed the internal queue used to confirm successfully sent messages and the
event listener associated with it.
- Made the HousekeeperJob read event entries in batches (the size is configurable)
to limit the max number of rows processed by each run (hence the messages sent)
- Introduced the content-type for the JMS event message in order to allow different
message serialization technologies (xml, json)
- Introduced session pooling in the JMSEventBus implementation to improve scalability
the changes are close to be finished, we'll notify the mailing list as soon as they'll be available in github.
Stefano
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Sunday, August 13, 2017 9:13:25 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] Kapua Service Events update
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Monday, August 7, 2017 11:14:56 AM
To: kapua developer discussions
Subject: Re: [kapua-dev] Kapua Service Events update
Hi all,
I worked a bit on the service events feature, refining the last proposal. Under the following path you will find a working solution:
https://github.com/stefanomorson/kapua/tree/feature-serviceEvents
finally I updated the document here:
https://docs.google.com/document/d/14Bsxg0l0gMnNzxtorcvm584wuveMANEGhdAOkCx2DrY/edit?usp=sharing
Cheers,
Stefano
From: Morson, Stefano
Sent: Friday, August 4, 2017 12:05 PM
To: Modanese, Riccardo; Codutti, Alberto; Evangelista, Elbert; Mezzasalma, Claudio
Cc: Carrer, Marco
Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events
Add:
- serialisation of the KapuaEvent
From: Morson, Stefano
Sent: Friday, August 4, 2017 10:30 AM
To: Modanese, Riccardo; Codutti, Alberto; Evangelista, Elbert; Mezzasalma, Claudio
Cc: Carrer, Marco
Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events
Points to solve for the demo:
1 - (Minimal) Realistic queue model implementing the idea exposed by Dejan and related broker setup
2 - Persistency for the KapuaEvent object
3 - Cleanup (marking) of the EventStore entries that match events successfully sent.
4 - Processing of the EventStore entries that match events not successfully sent (House Keeper).
5 - End-to-end test
6 - Reduce the number of files to the minimum.
6 - Port to develop using the minimum set
7 - End-to-end test
Stefano
From: Morson, Stefano
Sent: Friday, August 4, 2017 9:56 AM
To: Modanese, Riccardo; Codutti, Alberto; Evangelista, Elbert; Mezzasalma, Claudio
Subject: Fw: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Thursday, August 3, 2017 3:58 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Tuesday, August 1, 2017 9:37:03 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Monday, July 31, 2017 10:36:25 AM
To: kapua developer discussions
Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events
From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Dejan Bosanac <dbosanac@xxxxxxxxxx>
Sent: Thursday, July 27, 2017 6:09:23 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] Start to work on use-cases, failure scenarios for Kapua Service Events
|