Google App Engine developers can now access dedicated cache up to 20GB of memory and split the application in modules providing stateless and secure services.
Mozilla is scaling websites from thousands to hundreds of millions of users through simple scaling patterns they have learned internally according to Brandon Burton, web operations engineer at Mozilla. The lessons learned include caching, scaling out web servers, asynchronous jobs, and databases.
Around January 2011, Memcached became the number one caching solution based on Java developer job demand. Memcached expanded beyond its LAMP roots. InfoQ caught up with Dustin Sallings, the implementer of Spymemcached the leading Java Memcached client, to get his perspective on the rise of Memcached in the Java world.
In this presentation filmed during QCon SF 2008, Aditya Agarwal discusses Facebook’s architecture, more exactly the software stack used, presenting the advantages and disadvantages of its major components: LAMP (PHP, MySQL), Memcache, Thrift, Scribe.
In this presentation from RubyFringe, Tobias Lütke talks about memcached, the widely used caching solution. Tobias explains how to use it and gives some practical tips on what not to do.
The team at Delores Lab talk about lessons learned when their their site was featured on the Yahoo! home page, going from 500 to 100,000 visits overnight!
Shoal is a java clustering framework that provides infrastructure to build fault tolerance, reliability and availability for java application servers. It can also be plugged into any application that needs clustering and distributed systems capabilities. Shoal is the clustering engine for GlassFish and JonAS application servers and provides a distributed state cache for storing application state.
Exploring a couple of lesser known tools in the architects' scaling toolkit.
Instead of ASP.Net's built-in caching, some .NET developers are turning to memcached, is a distributed memory caching system originally by Danga Interactive for LiveJournal.
Rails performance expert Dr. Stefan Kaes takes a look at the most common performance issues in your Rails applications and what to do about them. Advice is given regarding benchmarking, choosing a session container, caching results of expensive computations, optimizing database queries and working effectively with view helpers.