I have an intranet database system where the header has a list of the last 5 orders viewed and the last 5 clients viewed.
The database is actually on Azure, while the website had to be moved to an Amazon server.
(Trust me, there were specific reasons we got stuck with this)
So, each page, I have to go to the DB and back to the server for both the information on the page and this stuff, which ONLY changes when the user looks at a job or client.
When everything was on Azure, it was pretty snappy, but now there's a clear lag. So here's my plan and maybe you folks can improve upon it.
(and I can't use session vars because we have load balancers, etc..)
It's really only about 1k of data.
Since a cookie gets posted back to the server with every page, there's that extra load between client and webserver, but perhaps that's worth the reduction in traffic between the DB and the webserver and the additional stored proc call on the DB?
What would be really nice would be a way I could just have a cookie that didn't post back, but just some HTML that could be cached on the user's machine. Maybe HTML5 has that?