Scott, thank you. Regarding messaging, I have two chief use cases: 1. Operational / Control messages. Expected to be low-velocity. Expected to have a degree of persistence, scale, failover, etc. 2. Data messages. Expected to be high to very/extremely high velocity (thousands+ messages per second). Need for persistence is optional. Fire-and-forget (no ack) support, etc.
Based on my knowledge of messaging those concerns fall mostly on the underlying message implementations (activemq/rabbitmq/kafka/etc.) themselves, rather than a client API. So, intuitively (and albeit naively as I haven’t done a full analysis yet) I’d assume I can use the event admin abstraction for both cases and swap out the underlying message implementations depending on independent concerns. That being said, I’d be inclined to just use it until such time that it doesn’t work (for example, the event admin implementation adds too much overhead, creates too much coupling to the OSGi platform or doesn’t support some level of message metadata that I’d need — these are all made-up examples). However, if you have walked this path before and have any pointers I’d greatly appreciate it! Thanks again! Derek Abdine On 3/15/14, 11:09 AM, "[email protected]" <[email protected]> wrote: >Hi Derek, > >> Thanks Felix! I¡¯ll take a look at these. By subsystems, do you mean >> subsystems of deployment admin or some other related OSGi service¡¦ ? >> >> Speaking of the event admin, is it common for this to be used for high >> velocity message piping through a formal message bus that may be >> distributed (i.e., rabbit, activemq, kafka, etc.)? Reading the spec a >> while ago I got the feeling that it was best used for lightweight >> in-container bundle communication. I¡¯d be interested in any known >> real-world uses if you happen to know of any. > >https://wiki.eclipse.org/Distributed_EventAdmin_Service > > >Scott > > >_______________________________________________ >OSGi Developer Mail List >[email protected] >https://mail.osgi.org/mailman/listinfo/osgi-dev This electronic message contains information which may be confidential or privileged. The information is intended for the use of the individual or entity named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify us by e-mail at ([email protected]) immediately. _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
