[aerogear-dev] UPS as WildFly Subsystem (was: UPS using JMS)

Mon May 11 04:50:13 EDT 2015

On Tue, Apr 7, 2015 at 9:49 AM, Lukáš Fryč <lukas.fryc at gmail.com> wrote:

> I reached out to Stian in order to fully understand the "Why" behind
> Keycloak offering a subsystem, and he identified two benefits:
>
> * smaller appliance downloads
> * easier to patch modules than monolithic WAR
>
> Can you see anything else?
>

* Easier configuration. Subsystem can provide both CLI and GUI
configuration layer for very small effort.

https://docs.jboss.org/author/display/WFLY8/Example+subsystem

>
> The question is how much relevant are these benefits for us, since we
> depend much more on Java EE (especially with JMS coming).
>
>
>
> In case of UPS, we can definitely strip some download Megabytes for
> (potential) appliance distribution (good for microservices oriented
> architectures),
>
> while still providing installation of subsystem to existing Wildfly EE
> instances. We can continue shipping WAR just for sake of backwards
> compatibility in case it will appear to be effortless.
>
>
>
> However I agree that UPS as WF subsystem is a direction worth to explore!
>
> ~ Lukas
>
>
>
>
>
> út 7. 4. 2015 v 9:18 odesílatel Matthias Wessendorf <matzew at apache.org>
> napsal:
>
>> Not sure, I think that was my question though
>>
>> On Tue, Apr 7, 2015 at 9:08 AM, Lukáš Fryč <lukas.fryc at gmail.com> wrote:
>>
>>> Do I read well that the subsystem would be the ONLY distribution
>>> mechanism?
>>>
>>> Created https://issues.jboss.org/browse/AGPUSH-1354 btw. Feel free to
>>> comment there.
>>>
>>> ~ Lukas
>>>
>>> pá 3. 4. 2015 v 13:50 odesílatel Matthias Wessendorf <matzew at apache.org>
>>> napsal:
>>>
>>> Cool stuff
>>>>
>>>> I am totally fine having this tied ti wf/eap
>>>>
>>>> wondering: at some point, should we offer a dist as (only) subststem
>>>> for wf/eap?
>>>>
>>>>
>>>> On Friday, April 3, 2015, Sebastien Blanc <scm.blanc at gmail.com> wrote:
>>>>
>>>>> That all sounds very good :)
>>>>> Thanks for the headupate, I will soon give it a try.
>>>>>
>>>>> On Fri, Apr 3, 2015 at 10:34 AM, Lukáš Fryč <lukas.fryc at gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi guys,
>>>>>>
>>>>>> so as outlined in previous thread [1], I have prototyped a JMS
>>>>>> batching approach for push message delivery.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> We've discussed the approach with Matthias, Mirek Novak and Ondrej
>>>>>> Chaloupka (EAP QE & JMS/JTA experts, thank you guys!) and these documents
>>>>>> describes a concept that we have came with:
>>>>>>
>>>>>> Diagram:
>>>>>> https://docs.google.com/a/fryc.eu/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing
>>>>>>
>>>>>> Text Doc:
>>>>>> https://docs.google.com/document/d/1X65P_U9O62Z5JZhKi9ZvBuZU1OrL4pNHNddlzJK6rMg/edit?usp=sharing
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Implementation-wise, I've so far prototyped the messaging part (split
>>>>>> SenderService functionality to two subsequent queues with MDBs as shown on
>>>>>> diagram),
>>>>>>
>>>>>> but that's just a start, since we must configure it appropriately for
>>>>>> efficiency (queue configuration and batch sizes) and verify that
>>>>>> configuration works as expected,
>>>>>>
>>>>>> the prototype lives on a branch (unpolished, to be squashed later):
>>>>>> https://github.com/lfryc/aerogear-unifiedpush-server/tree/jms-batching
>>>>>>
>>>>>> Off course, you can play with it already. :-)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> Apart from the new requirement of using Java EE full profile (JMS),
>>>>>> the prototype leverages implementation-specific configurations and APIs:
>>>>>>
>>>>>>    - org.hibernate.Query for token streaming / batch fetching
>>>>>>    - HornetQ configurations of queue size, blocking behavior and
>>>>>>    message de-duplication
>>>>>>
>>>>>> That pretty much binds us to WildFly/EAP - we can tweak it to run on
>>>>>> any compliant app server, but without specific configurations it won't work
>>>>>> properly.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Once configured and functionally tested (that can even wait for Beta2
>>>>>> I guess),
>>>>>>
>>>>>> we can cooperate with Mobile QE on testing (Stefan, Adam), their test
>>>>>> suite contains mocks of APNS/GCM against which we can load test.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Cheers!
>>>>>>
>>>>>> ~ Lukas
>>>>>>
>>>>>>
>>>>>> [1]
>>>>>> http://aerogear-dev.1069024.n5.nabble.com/aerogear-dev-UnifiedPush-new-requirement-JMS-Java-EE-Full-profile-tp11268.html
>>>>>>
>>>>>> _______________________________________________
>>>>>> aerogear-dev mailing list
>>>>>> aerogear-dev at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Sent from Gmail Mobile
>>>> _______________________________________________
>>>> aerogear-dev mailing list
>>>> aerogear-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>  _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20150511/df1b2f76/attachment-0001.html 