Link Details

Performance always becomes priority one after the proof of concept, no matter how hard we argue to refactor the prototype. But we as developers adapt and move forward. So your system produces an output, of course there are enhancements you could make to this process, but the biggest enhancement will be to cache the outputs for every user following the poor soul who endures the cache miss. So the task is made and assigned to you, what do you use?

Posted by nicholastuck  |   Mar 06 2011 / 13:46

Add your comment

Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Recommended Links

Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone