« Sponsored Post: ezRez, VoltDB and Digg are Hiring | Main | DynaTrace's Top 10 Performance Problems taken from Zappos, Monster, Thomson and Co »

Hot Scalability Links for July 17, 2010

And by hot I also mean temperature. Summer has arrived. It's sizzling here in Silicon Valley. Thank you air conditioning!

Reader Comments (6)

agastiya tweets, "Focus on stability and features first, scalability and manageability second, per-unit performance last of all."

I don't really agree with the last part of of this one. I think performance is a feature. A fast website is a usable website.

July 17, 2010 | Unregistered CommenterGreg Linden

Not to blow my own horn too much, but the tweet from agastiya is actually a quote from me.

July 17, 2010 | Unregistered CommenterJeff Darcy

Sorry Jeff, I didn't see the link tucked at the end. I added a reference to your post.

July 17, 2010 | Registered CommenterTodd Hoff

Oh, in the full context of Jeff's (not agasitya's) quote, I agree with him. He is talking about premature optimization, focusing on performance for performance sake, without regard to whether it actually impacts the user experience. The only point I wanted to make is that performance of the website from the user's point of view is important, since it is a factor in usability and satisfaction. But that is a lot different than focusing on performance timings before you know if those performance optimizations are noticeable to people who are using the website.

July 18, 2010 | Unregistered CommenterGreg Linden

Definitely agree Greg.

July 19, 2010 | Registered CommenterTodd Hoff

Forethought is the most important activity in web service development, the decisions up front can save you from so much pain, important scalability questions to ask up front...1) If we build out the infrastructure to handle peak load for a given time period, how do we use that infrastructure in the non-peak days/hours to monetize or capture revenue, (idle infrastructure verses latency on peak loads) 2) Carefully plan the platform services that are critical to scaling : DNS/DHCP/NTP, User MGMT, OS PROP, CODE PROP, Trusted Host, Monitoring, Policy & Configuration Mgmt, Rapid provisioning, automated differentiation, load balancing etc..3) HW fails and load balancing is the norm: write code and use apps that incorporate strategies for risk mitigation when failures occur...4) shard/replicate data that is important so you dont lose sleep, 5) Decouple, use asynchronous communications, "code smart" for load balanced stateless programming wherever you can.

That's off the top of my head, but still, tenets to live by.

July 22, 2010 | Unregistered CommenterEvan Bradley

PostPost a New Comment

Enter your information below to add a new comment.
Author Email (optional):
Author URL (optional):
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>