On Mon, Jun 6, 2016 at 9:21 PM, Manuranga Perera <[email protected]> wrote:
> I think as much as possible we have to achieve this with Event-driven >> architecture rather than schedulers. >> > +1 > Let's take an example. Say we use event driven pattern here and we have substitution from user A to user B which is defined at T0, starts at T1 and end at T10. Currently User A has x number of in-progress tasks. Let's say, engine hasn't received any new task creation requests for this particular user during T1-T5. Then engine will not able to reassign above X tasks back to user B during this time period. But user B should able to perform above task after T1. This is why we can't use event driven pattern here. > So we can use simple cache mechanism as below > > While this is possible, I don't see why we are trying to shave off a few > milliseconds from the task creation and make the it more complex even > sacrificing correctness. Isn't this some premature optimization ? > > -- > With regards, > *Manu*ranga Perera. > > phone : 071 7 70 20 50 > mail : [email protected] > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > Thanks, Hasitha. -- -- Hasitha Aravinda, Associate Technical Lead, WSO2 Inc. Email: [email protected] Mobile : +94 718 210 200
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
