Click here to Skip to main content
15,887,596 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Assume that you are developing a web application that shows currency exchange rates for a bank web site. The rates are stored in an IBM Mainframe in the bank and rates are available through web services. Each time a user accesses the rates page, the page makes a request to the mainframe. This generates too much load on the mainframe. Especially most of the time the rates delivered is the same. But at the same time rates may fluctuate within the day and if rates have changed the web page should not display the cached values but make another request to the web service. The rates table at mainframe supports triggers where each update to the rates table can invoke a trigger where the trigger may further call a web service. How would you design such a caching architecture and make sure it is invalidated on rate changes? Please explain by drawing a diagram.

Thanks
Hadley
Posted

1 solution

We do not do your homework: it is set for a reason. It is there so that you think about what you have been told, and try to understand it. It is also there so that your tutor can identify areas where you are weak, and focus more attention on remedial action.

Try it yourself, you may find it is not as difficult as you think!

If you meet a specific problem, then please ask about that and we will do our best to help. But we aren't going to do it all for you!
 
Share this answer
 

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900