in my assignement i have to model a web application for allows customare to view calls/traffic of own mobile details.
in first version of my solution, the customare invoke service (by web page) and he obtains all data in a row. all details are put in the HTTPSession. Further request for details are served from HTTPSession.
i want to review this solution (tell me if i wrong) by deleting all data in Session (EJBSession too) and i want to make call for details on fly.
what do you think about it?
Whether to cache the data in the session depends on your performance and failover requirements. Also, note that you shouldn't be caching the data in both the HttpSession and EJB stateful bean. Pick one. Having it in both is redundant.
my caching solution isn't both session, but one o them.
performance requirement is that all pages would be dislpayed in 3 seconds.
the scalability requirement could be tricky: customare base will grow by 1000% the first year.
Joined: Mar 30, 2014
and what about replication of data?
metersystem, external system written in java, track the customare usage.
which is better choose:
-for every details our system calls the metersystem (by EJB/RMI): one call to metersystem for each customare request for details
-replication of details data inside our system: there is a batch that makes one call to metersystem for replication of details, in this way every request for details is inside the system.
What do you think about that?
some considerations please?