gpoul's Out Of Memory Blog

Billy Newport wrote a very interesting post about using partitioning to speed up debit/credit applications.

The lesson I take away from this is that you can use existing patterns and apply them to applications where before you thought it won’t make much sense because you didn’t understand the load pattern. Understanding not only what your application is doing and how your application is performing work, but also how often it is performing specific kind of work is very important for optimizing them and finding the right patterns to use. – This is common knowledge for performance testing because you need to find the right load to test your application, but oftentimes it’s very hard to gather this data even that late into the project. If you think about this in the architecture phase of a project, it not only is available to you when it comes to performance testing, but you already optimized your application’s architecture to this load pattern.