Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [kapua-dev] Kapua Service Events update

Hi,


changes have been published to GitHub:


https://github.com/stefanomorson/kapua/tree/feature-serviceEvents



Stefano

From: kapua-dev-bounces@xxxxxxxxxxx <kapua-dev-bounces@xxxxxxxxxxx> on behalf of Morson, Stefano <stefano.morson@xxxxxxxxxxxx>
Sent: Thursday, August 24, 2017 3:13:47 PM
To: kapua developer discussions
Subject: Re: [kapua-dev] Kapua Service Events update
 

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
 

Hi all,


I wanted to share the latest changes for the Service Events implementation based in the EventStore proposal. The code is available at the following url:


https://github.com/stefanomorson/kapua/tree/feature-serviceEvents


I prepared a quick guide for building and running the application along with a short overview:


https://docs.google.com/document/d/1AGeOFScnbbAgTx76ebMcxzAONKN3k4rclNINa0_JNLI/edit?usp=sharing



Cheers,

Stefano

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
 

Hi all,


I updated the document adding a new session and a reviewed proposal for the Event Store based approach. Here is the link:


https://docs.google.com/document/d/14Bsxg0l0gMnNzxtorcvm584wuveMANEGhdAOkCx2DrY/edit?usp=sharing


Cheers,

Stefano

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
 

Hi all,


during the weekend I worked a bit to clarify and generalise the requirements and the use cases for the service events. Here is the link to the document:



https://docs.google.com/document/d/14Bsxg0l0gMnNzxtorcvm584wuveMANEGhdAOkCx2DrY/edit?usp=sharing


Cheers,

Stefano

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
 
Hi everyone,

here's a recording of the today's meeting https://bluejeans.com/s/f1FoH

On Thu, Jul 27, 2017 at 12:35 PM, Morson, Stefano <stefano.morson@xxxxxxxxxxxx> wrote:

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


Am 26.07.2017 um 10:22 schrieb Jens Reimann <jreimann@xxxxxxxxxx>:

Hi,

as discussed in the last meetings around Kapua Service Events, I did start working on describing a few use-cases we want to cover with those service events and which failure scenarios can arise.

I just wanted to share my current state with you via a Google Doc:

https://docs.google.com/document/d/1J5ilkg0dksEfkdQ_bN2uCREMIs70Fszes5SSs8hK8H8

Please feel free to comment and make suggestions.

Cheers

Jens

--
Jens Reimann
Senior Software Engineer / EMEA ENG Middleware
Werner-von-Siemens-Ring 14
85630 Grasbrunn
Germany
phone: +49 89 2050 71286
_____________________________________________________________________________

Red Hat GmbH, www.de.redhat.com,
Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Paul Argiry, Charles Cachera, Michael Cunningham, Michael O'Neill
_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev


_______________________________________________
kapua-dev mailing list
kapua-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/kapua-dev




--

Back to the top