All changes go through the app server layers, written to the cache layer which then distributes them out to the other caches and back to the database. There are even standards on this technology emerging, I suspect MS will have a product around it soon enough.
Richard --- Richard Vowles, Solutions Architect, Borland New Zealand email: [EMAIL PROTECTED] phone: +64-9-9184573 cell: +64-21-467747 other: MSN [EMAIL PROTECTED], skype: rvowles blog: http://www.usergroup.org.nz/blogs/selectBlog.html?id=39769 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Heinz Sent: Thursday, 1 June 2006 5:35 p.m. To: NZ Borland Developers Group - Delphi List Subject: RE: [DUG] Why InterBase Richard wrote: > Application server layers are scalable, you can just add more of them. > There are more and more people who wish to scale adding distributed > caches as well (open source ones), where the entire database is sucked > into memory and the distributed cache deals with everything, making it > ever so much more scalable. They work, they are in operation, you just > have to have a bit more money for machines that can have lots of memory. Hrmm... how does that work? If you add lotsa application servers and they all pull the database into memory, how to you keep these caches coherent with changes in the database? _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
