News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Scott Mattocks:
I is for Isolation
January 16, 2013 @ 12:02:23

Scott Mattocks has posted the next "letter" in his LUCID development series (more here) - the I is for Isolation:

Applications are a collection of individual components; they pull together the contributions of individuals to create something which is greater than the sum of its parts. If one piece breaks down, and the system is not prepared to put it in quarantine, the entire application can come crashing down. [...] The best way to stave off this infection is to prevent it at the source. Keep the application happy by making it more resistant to implosion.

He talks about the "code jerks" of your application that hog resources or functionality and cause general problems for the application as a whole. He notes that sometimes it's the result of a third party, but it can also be internal (and more difficult to find). He gives a more specific example of a database wrapper class and some suggestions of things to do as failover (ex. used cached data or read from a secondary).

0 comments voice your opinion now!
lucid development principles isolation series


blog comments powered by Disqus

Similar Posts

IBuildings Blog: Book Review: TYPO3 Extension Development

Zend Developer Zone: The ZendCon Sessions Episode 8: Building Scalable Development Environments

Fabien Potencier's Blog: Create your own framework... on top of the Symfony2 Components (part 12)

John Cox\'s Blog: Book Review - XML Web Development

Sebastian Bergmann's Blog: Using Bazaar for PHPUnit Development


Community Events





Don't see your event here?
Let us know!


deployment introduction voicesoftheelephpant language conference threedevsandamaybe framework symfony release podcast list interview community tips series api laravel bugfix code zendserver

All content copyright, 2014 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework