Hi Sachith, If the use-case is to display the 1 hour analytics data from CEP, then IMO the he/she need to simply store the CEP results into a persistence store (DAS or RDBMS via RDBMS event publisher), and then let the gadget read from the persistence store. I don't think caching is a good option in such cases because anyhow if the server crashes due to some reason the data is not going to be shown.
Thanks, Sinthuja. On Wed, Jul 6, 2016 at 10:12 PM, Sachith Withana <[email protected]> wrote: > Hi all, > > In the dashboard, the real time data is only shown if the user is logged > into the dashboard at the time of the data is being pushed. > > If the data is being pushed every hour, a new user who logs in would > potentially have to wait up to one hour to see the real time data, and if > the user refreshes, then has to wait another hour to see the data, and > would loose the current data completely. > > I understand from the CEP perspective it's similar to fire and forget, but > can't we add some level of caching to prevent this? > > Regards, > Sachith > -- > Sachith Withana > Software Engineer; WSO2 Inc.; http://wso2.com > E-mail: sachith AT wso2.com > M: +94715518127 > Linked-In: <http://goog_416592669> > https://lk.linkedin.com/in/sachithwithana > -- *Sinthuja Rajendran* Technical Lead WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
