Channels ▼

Developer Reading List

, December 03, 2013 Ruby, Python, ASP.NET, Android development, PDF, and more.
  • E-mail
  • Print

Building Fast ASP.NET Websites

by Dean Alan Hume

It seems inevitable these days that developers will be dragged into website development at one point or another in their work. When they are, they will quickly discover that the problems are multifarious: coding for incompatible browsers, testing, security, and performance. This book squarely takes on the last of these and does an excellent job explaining the problems and detailing the solutions.

The author presumes only basic technical knowledge, so he starts off with a refresher on how exactly HTTP verbs operate and what actually happens when an application interacts with a client. Then building on that base, he examines the sources of performance problems. To do this, he first discusses the tools that measure page load times and other contributors to performance and shows how to interpret their data.

He then explores solutions such as caching and its numerous complexities, minifcation and compression, HTML optimization, and other techniques. While some of the implementation details are presented in terms of ASP.NET, almost everything in this book could be applied to any website. The issues are essentially the same across Web servers and the solutions often vary in predictable ways.

The text is designed as a handbook: The tone is eminently practical and the contents intended for immediate application. This is most evident in the author's frequent mentions of specific tools and solutions — the latter including even content delivery network (CDN) options.

The only limitation I find in this rather admirable little volume is its brevity. The author barely touches on measuring and improving performance under load (nor even load balancing) and he almost never mentions security — so it's not entirely clear that his recommendations scale properly or whether they present opportunities for crackers. In addition, websites built in the cloud — the clear path forward for future development — is not discussed at all. More coverage of these topics would have made this an ideal volume.






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.