You’re interested in web application scalability and availability, right? Of course you are! Well, you’re in luck because Udi Dahan – enterprise development expert, SOA specialist and author of NServiceBus – joins the guys on this week’s episode of Herding Code.
- Jon kicks off the show by asking Udi if one can run a high-availability and high-scalability site (like stackoverflow.com) on two servers with ASP.NET? Udi asks “how high is high” and talks about the importance of defining the scope of the architectural problem.
- Udi comments on the how site behavior (high reads or writes, static or dynamic content, etc) dictates the way availability and scalability concerns can be handled.
- Udi talks about how websites can be broken into fragments and how one can take advantage of content distribution networks and caches.
- Udi stresses that high-availability inherently makes scaling more difficult and how scalability is a multidimensional cost function.
- Kevin asks about common scalability mistakes and solution patterns. Udi replies with talk of SOA, web services, REST, one-way messaging, pub/sub and offloading things to the background in an asynchronous way.
- Kevin follows up with additional questions: Why don’t more developers turn to messaging patterns to solve their scalability issues and can one introduce scalability changes incrementally?
- Udi discusses the scalability patterns employed by RIA Services for Silverlight and gives his opinion on Azure as a scalability system.
- Scott K asks about geographical distribution and Udi gets to the heart of the matter – high-availability means writing data to multiple places which means you are slowing your system down.
- K Scott asks Udi about the AppFabric service bus provided by Microsoft and how it compares to already available distributed cache solutions like .NET Service Bus, MassTransit, and NServiceBus.
[Note: The sound quality for Udi's voice is kind of rough. We tried to clean it up, and this is as good as it's going to get. Just pretend we're talking to him on a CB and things will be fine]
Show Links:
Download / Listen:
Herding Code 67 – Udi Dahan on Scalability
Audio clip: Adobe Flash Player (version 9 or above) is required to play this audio clip. Download the latest version here. You also need to have JavaScript enabled in your browser.
Show notes compiled by Ben Griswold. Thanks!
Jan
10
This entry was posted
on Sunday, January 10th, 2010 at 1:00 amand is filed under interview.
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.
4 Comments Herding Code 67: Udi Dahan on Scalability
Mike Chaliy
January 11th, 2010 at 11:50 am
I believe that .NET Service Bus, MassTransit, and NServiceBus is not distributed cache solutions. This is mistake or I missed something?
Scalability Podcast on Herding Code
January 11th, 2010 at 12:44 pm
[...] Click here for the full list of topics and to download the podcast. [...]
Tweets that mention Herding Code 67: Udi Dahan on Scalability | Herding Code -- Topsy.com
January 12th, 2010 at 7:28 pm
[...] This post was mentioned on Twitter by Elijah Manor, Jon Galloway, Scott Koon, K. Scott Allen, UdiDahan and others. UdiDahan said: It's been a while since I was on a podcast. Today the good folks at Herding Code put up our discussion on scalability: http://bit.ly/72U2OO [...]
James
January 19th, 2010 at 5:03 am
Mike, it’s not a mistake. They’re service buses and that’s a completely different beast from a distributed cache like memcached or velocity.
RSS feed for comments on this post · TrackBack URI
Leave a Reply