tag:blogger.com,1999:blog-13465455.post1276390366193474327..comments2024-02-05T03:19:14.204-05:00Comments on Ash's Identity Management Rantings: More on VDS and CacheAshraf Motiwalahttp://www.blogger.com/profile/06659523320698728171noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-13465455.post-27949598131975407502009-08-05T18:31:09.027-04:002009-08-05T18:31:09.027-04:00We usually like to use persistent caching in insta...We usually like to use persistent caching in instances where the performance/availability on some of our backend data stores housing universally interesting information is spotty.<br /><br />We could spend money and upgrade that data store's servers or spend even more money to create a real metadirectory solution and replicate the data off somewhere else. Spending that money is pretty hard to justify, though, when persistent caching is (relatively) cheap.Quignoreply@blogger.comtag:blogger.com,1999:blog-13465455.post-49133355802096991402009-05-05T05:03:00.000-04:002009-05-05T05:03:00.000-04:00cheap wow power leveling buy wow gold cheapest wow...cheap <A HREF="http://www.wowpowerleveling.me/" REL="nofollow">wow power leveling</A> buy <A HREF="http://www.wowgold-powerleveling.com/" REL="nofollow">wow gold</A> cheapest <A HREF="http://www.wowgold-powerleveling.com/" REL="nofollow">wow power leveling</A> CHEAP <A HREF="http://www.wowpowerleveling.me/" REL="nofollow">wow gold</A> BUY <A HREF="http://www.wowgold-powerleveling.com/" REL="nofollow">power leveling</A> CHEAPEST <A HREF="http://www.wowgold-powerleveling.com/" REL="nofollow">wow powerleveling</A> <br /><A HREF="http://www.globalsale.me/" REL="nofollow">wow gold</A><A HREF="http://www.cheapgamegold.org" REL="nofollow">wow gold</A><A HREF="http://www.cheap-gamegold.org" REL="nofollow">wow gold</A><A HREF="http://www.gamegoldvip.org" REL="nofollow">wow gold</A>weiweiwow power levelinghttp://www.wowpowerleveling.menoreply@blogger.comtag:blogger.com,1999:blog-13465455.post-12492449372090072009-02-18T08:32:00.000-05:002009-02-18T08:32:00.000-05:00Ash, Symlabs comments can be found here http://blo...Ash, Symlabs comments can be found here<BR/><A HREF="http://blog.symlabs.com/identity-matters-journal/2009/2/17/virtual-directory-servers-and-cache.html" REL="nofollow"> http://blog.symlabs.com/identity-matters-journal/2009/2/17/virtual-directory-servers-and-cache.html </A>Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-13465455.post-74152597292302684282009-02-13T22:10:00.000-05:002009-02-13T22:10:00.000-05:00The great thing about virtual directories is the f...The great thing about virtual directories is the flexibility. In some cases you may not need to cache, but in other situations those types of capabilities can be useful. There are many ways to use caching in the world of virtual directories. A simple example is as follows:<BR/><BR/>* Company A is made up of 10 divisions that are overseen by a parent company<BR/>* The parent company is located in Chicago while the divisions are scattered across the country<BR/>* Historically each division has hosted their own identity infrastructure<BR/>* The parent company processes all contracts and has the master repository for customer entitlement information - this repository is in a database that is only located in Chicago and can not be easily replicated<BR/>* Company A has a long term vision that they will one day be able to consolidate their identity infrastructure all within the parent company but that is years away<BR/>* Branch 1 has several customer facing applications that authenticate users against a local LDAP directory<BR/>* Branch 1 has a new customer facing application that requires the ability to restrict access to information based upon the products the customer has purchased<BR/><BR/>There are probably many ways to solve this problem, but since we are talking about virtual directories... By setting up an instance of the virtual directory at Branch 1 I can then:<BR/><BR/>* Create a cached view of the information from the database in Chicago<BR/>* Set up a proxied view of the users in the local LDAP directory<BR/>* Join the user information proxied from the local LDAP with the cached information from the database<BR/><BR/>This provides the additional information that the new application requires without the application needing to change anything except perhaps an IP address. At the same time delivers the benefit of not traversing the WAN repeatedly for authorization information.<BR/><BR/>So, it is a benefit to have options like this.<BR/><BR/>ToddAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-13465455.post-42694564459893608132009-02-13T16:54:00.000-05:002009-02-13T16:54:00.000-05:00Ash, I think you make some good points and its wor...Ash, I think you make some good points and its worth looking at further to clarify what we are really talking about... <BR/><BR/>http://identityinfrastructure.blogspot.com/2009/02/why-cache-and-virtual-directories.htmlTPShttps://www.blogger.com/profile/15738219556065262084noreply@blogger.comtag:blogger.com,1999:blog-13465455.post-48856224915312800982009-02-13T15:40:00.000-05:002009-02-13T15:40:00.000-05:00Ash, my 2 cents here:http://360tek.blogspot.com/20...Ash, my 2 cents here:<BR/>http://360tek.blogspot.com/2009/02/weighing-in-on-persistent-cache.htmlMatt Flynnhttps://www.blogger.com/profile/09902381553517250020noreply@blogger.com