Comments on: High-Performance DNS for The Cloud http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/ A goal is a dream with a deadline. Thu, 11 Mar 2010 05:00:55 +0000 http://wordpress.org/?v=2.7.1 hourly 1 By: Ilya Grigorik http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/comment-page-1/#comment-224860 Ilya Grigorik Wed, 02 Dec 2009 14:59:14 +0000 http://www.igvita.com/?p=193#comment-224860 Michal, if you control the hardware, you should be able to just reassign the IP address to a different MAC at will, effectively achieving the same service as Elastic IP. Having said that, you're right, an automated heartbeat + failover is a good thing to have! HA Linux and others is probably what you're what looking for. Although, I'm sure there are hardware solutions for this as well... Michal, if you control the hardware, you should be able to just reassign the IP address to a different MAC at will, effectively achieving the same service as Elastic IP. Having said that, you’re right, an automated heartbeat + failover is a good thing to have! HA Linux and others is probably what you’re what looking for. Although, I’m sure there are hardware solutions for this as well…

]]> By: Michal Frackowiak http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/comment-page-1/#comment-224859 Michal Frackowiak Wed, 02 Dec 2009 14:28:56 +0000 http://www.igvita.com/?p=193#comment-224859 Yes, Elastic IPs are great, if you are using EC2 - you could set up a new server, even just to forward traffic. However in conventional datacenters this is much more problematic - and we are facing this right now, having to design system that should distribute traffic to a dozen of equal servers. Anyway, the DNS balancer is a very good first-line solution, which can be supplemented by internal failover mechanisms, like EIP switching in EC2, or an equivalent mechanism in other datacenters or providers. Yes, Elastic IPs are great, if you are using EC2 - you could set up a new server, even just to forward traffic.

However in conventional datacenters this is much more problematic - and we are facing this right now, having to design system that should distribute traffic to a dozen of equal servers.

Anyway, the DNS balancer is a very good first-line solution, which can be supplemented by internal failover mechanisms, like EIP switching in EC2, or an equivalent mechanism in other datacenters or providers.

]]> By: Ilya Grigorik http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/comment-page-1/#comment-224858 Ilya Grigorik Wed, 02 Dec 2009 14:15:42 +0000 http://www.igvita.com/?p=193#comment-224858 Michal, that's when services like Amazon's Elastic IP come in handy. Simply take that IP address (of the failed node) and reassign it to a different server. Takes ~dozens of seconds for the full switch on EC2. Michal, that’s when services like Amazon’s Elastic IP come in handy. Simply take that IP address (of the failed node) and reassign it to a different server. Takes ~dozens of seconds for the full switch on EC2.

]]> By: Michal Frackowiak http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/comment-page-1/#comment-224857 Michal Frackowiak Wed, 02 Dec 2009 13:56:06 +0000 http://www.igvita.com/?p=193#comment-224857 DNS is indeed a cheap load balancing tool. But what if one of your frontend nodes fail? Good if you have low TTL, but if some ISPs cache your DNS records for 24 hours? Any recommendations here? DNS is indeed a cheap load balancing tool. But what if one of your frontend nodes fail? Good if you have low TTL, but if some ISPs cache your DNS records for 24 hours?

Any recommendations here?

]]> By: Ilya Grigorik http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/comment-page-1/#comment-134235 Ilya Grigorik Tue, 23 Sep 2008 12:26:33 +0000 http://www.igvita.com/?p=193#comment-134235 Ah, that's a good one. If we need to keep databases in sync, we'll take the most recent snapshot, bring it up and set it up as a slave of the current production database. Then, when we flip the switch on DNS, we reverse the relationship between the databases. That way, we can still do a live rollback. Of course, if part of the upgrade are database schemas, then it gets a bit more complicated. Ah, that’s a good one. If we need to keep databases in sync, we’ll take the most recent snapshot, bring it up and set it up as a slave of the current production database. Then, when we flip the switch on DNS, we reverse the relationship between the databases. That way, we can still do a live rollback.

Of course, if part of the upgrade are database schemas, then it gets a bit more complicated.

]]> By: Mean Business » Blog Archive » links for 2008-09-23 http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/comment-page-1/#comment-134200 Mean Business » Blog Archive » links for 2008-09-23 Tue, 23 Sep 2008 09:00:41 +0000 http://www.igvita.com/?p=193#comment-134200 [...] High-Performance DNS for The Cloud - igvita.com (tags: AWS cloud deployment architecture) [...] [...] High-Performance DNS for The Cloud - igvita.com (tags: AWS cloud deployment architecture) [...]

]]> By: W. Andrew Loe III http://www.igvita.com/2008/09/22/high-performance-dns-for-the-cloud/comment-page-1/#comment-134009 W. Andrew Loe III Mon, 22 Sep 2008 16:47:10 +0000 http://www.igvita.com/?p=193#comment-134009 How do you deal with database drift during the transition? Do you just point your new infrastructure at your production database and migrate it, designing so that your changes are backwards compatible? How do you deal with database drift during the transition? Do you just point your new infrastructure at your production database and migrate it, designing so that your changes are backwards compatible?

]]>