Under most circumstances, caching data does not seem too outlandish. So why should it be for the Web 2.0 business?
Danny Ayers has an interesting post detailing why and how caching can be used on the Web to meet scaling requirements for Web 2.0 services. Danny wrote:
“If the Web is the platform, then as much of the data that isnít entirely application-specific must be exposed in such a way to allow it to be devolved to other parts of the Web. Use of existing Web-based data (i.e. other peopleís exposed stores) shouldnít be the exception, it should be the rule. This mean that for the system to be robust, there will be more work on caching, and less on the construction of disconnected data silos. Caching is one of the key features that has enabled Web 1.0 to scale.”
By this Danny means not just using open source technologies like Apache, PHP and MySQL for data storage – but using open XML-based data standards like RSS and Atom. Danny goes as far as to say that a startupís software should “consist of three parts commodity to one part unique”, with a lot of commodity being the data formats and storage in an application. So what will be the unique parts of an app? Danny suggested user interface and some of the data processing, as two examples. [Read the rest]