Performance tradeoff

I just came across an interesting post about performace antipatterns in my RSS readerthis morning and I couldn’t agree more on 99.9 % of the contents.  There are two comments I feel are worth making though.

Layering is, of course adding extra noise to applications, but there are just so many instances where incorrect layering is causing serious quality problems. Big-ball-of-mud being one my peronal favourite among them.  A properly layered architecture should also reduce the number of WTF’s  per minute dramatically.

Reuse. In  a normal scenario, you’ll be doing several things in multiple scenarios, to keep yourself DRY, reuse is a must. Not only is this also a WTF/minute reducer but it aids in testability, development speed and consistency as well.

The quoute at the end sums this up nicely

Software reuse is a fine goal, but beware of violating the assumptions made during its development

The key points of this is that there are circumstances where it is necessary to trade some of the overall performance (in throughput) for quality and speed of development.

 

/J

Advertisements



    Leave a Reply

    Fill in your details below or click an icon to log in:

    WordPress.com Logo

    You are commenting using your WordPress.com account. Log Out / Change )

    Twitter picture

    You are commenting using your Twitter account. Log Out / Change )

    Facebook photo

    You are commenting using your Facebook account. Log Out / Change )

    Google+ photo

    You are commenting using your Google+ account. Log Out / Change )

    Connecting to %s



%d bloggers like this: