[aerogear-dev] UPS using JMS update
Lukáš Fryč
lukas.fryc at gmail.com
Fri Oct 23 05:35:12 EDT 2015
Hi guys,
as first major UPS release (1.1.0) with JMS-based token batching will be
landing soon,
just wanted to document how it can be configured for optimal throughput and
failover, just in case someone wants to play with that right now:
https://docs.google.com/drawings/d/13IsJWPSJNYXtst-UVxQYmzH36C_EXQMYYr_jcu7nFmE/edit?usp=sharing
https://issues.jboss.org/browse/AGPUSH-1420
Cheers,
~ Lukas
On Wed, Apr 8, 2015 at 5:57 PM, Lukáš Fryč <lukas.fryc at gmail.com> wrote:
> Okay, first prototype is reading for testing and review:
> https://github.com/aerogear/aerogear-unifiedpush-server/pull/522
>
> po 6. 4. 2015 v 20:17 odesílatel Jay Balunas <jbalunas at redhat.com> napsal:
>
> This all sounds really good to me! The priority would be wf/eap imo, with
>> others if very easy, or if community members want to jump in and add their
>> favorite.
>>
>> On Fri, Apr 3, 2015 at 7:54 AM, Sebastien Blanc <scm.blanc at gmail.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Apr 3, 2015 at 1:50 PM, Matthias Wessendorf <matzew at apache.org>
>>> wrote:
>>>
>>>> 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?
>>>>
>>> +1, I was exactly thinking the same, since we are tied to wf/eap,
>>> subsystem makes a lot of sense IMO
>>>
>>>
>>>>
>>>>
>>>> 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
>>>
>>
>> _______________________________________________
>> 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/20151023/94fe6172/attachment.html
More information about the aerogear-dev
mailing list