[New Architecture] Event Messaging System Proposal

[Imesh Gunaratne <im...@apache.org>]

Hi All,

The following diagram illustrates a proposal for the Event Messaging System
in New Stratos Architecture:

[image: Inline image 2]

*Message Publisher*
Events could be implemented as Plain Java Objects containing necessary
property values to describe the event to the subscriber. Thereafter the
event object could be put into a event message object and it's header could
be used to define message header properties such as event class name,
time-stamp, etc. Once the event message is ready to be sent it could be
transformed into a JSON object and published to the message broker topic as
text.

*Message Subscriber*
This could be implemented in any preferred language which could talk to the
Message Broker. The Message Processor could first read the header and find
the event class name and decide whether to de-serialize the complete
message or not.

*Key Features*
- Multiple types of events could be sent through the same topic.
- Events could be identified without parsing the entire message.
- Messaging system is not coupled with the event definitions.

Please feel free to add you thoughts.


Many Thanks
Imesh






-- 
Imesh Gunaratne
Committer & PPMC Member | Apache Stratos (Incubating)
Technical Lead | WSO2 Inc

Re: [New Architecture] Event Messaging System Proposal

[Imesh Gunaratne <im...@apache.org>]

Correction: your thoughts

Thanks
Imesh


On Mon, Oct 14, 2013 at 10:11 AM, Imesh Gunaratne <im...@apache.org> wrote:

> Hi All,
>
> The following diagram illustrates a proposal for the Event Messaging
> System in New Stratos Architecture:
>
> [image: Inline image 2]
>
> *Message Publisher*
> Events could be implemented as Plain Java Objects containing necessary
> property values to describe the event to the subscriber. Thereafter the
> event object could be put into a event message object and it's header could
> be used to define message header properties such as event class name,
> time-stamp, etc. Once the event message is ready to be sent it could be
> transformed into a JSON object and published to the message broker topic as
> text.
>
> *Message Subscriber*
> This could be implemented in any preferred language which could talk to
> the Message Broker. The Message Processor could first read the header and
> find the event class name and decide whether to de-serialize the complete
> message or not.
>
> *Key Features*
> - Multiple types of events could be sent through the same topic.
> - Events could be identified without parsing the entire message.
> - Messaging system is not coupled with the event definitions.
>
> Please feel free to add you thoughts.
>
>
> Many Thanks
> Imesh
>
>
>
>
>
>
> --
> Imesh Gunaratne
> Committer & PPMC Member | Apache Stratos (Incubating)
> Technical Lead | WSO2 Inc
>