Verizon Wireless finally has the iPhone 4. There have been commercials running for the iPhone by both Apple and Verizon for the past month. Fans rejoice, our savoir has arrived. . . right? You couldn’t be more wrong.
The iPhone is coming out during a time when 4G and dual core phones have already been announced or are already out in stores by some carriers. Verizon is potentially weeks away from releasing their next gen 4G dual-core phone running on Android. Now that is drool worthy.
The iPhone 4 is a nice addition to Verizon’s lineup, but it’s too late to jump on the Apple train. True, we should be happy that it is here and when Apple gets around to releasing iPhone 5 then it will certainly be worth the hype, but for now do yourself a favor and hold off.
It’s been a few months now since Amazon Route 53 was released to the public. Some of you may have forgotten about it, while others are hesitant to change their DNS servers because there may not be much upside to it. Lucky for you, I couldn’t help myself and jumped on board within the first week of it being released. I have never experienced any DNS issues since the switch and from my untrained eye, things seemed to be more consistent. But what I really wanted was a reliable Amazon Route 53 benchmark to prove it.
Here is a DNS benchmark comparison of FantasySP.com provided by indeep76.com. Below you’ll see how much of an improvement Route 53 makes from various locations:
During the last 2-3 months using Amazon Route 53, the DNS lookups are more consistent and more reliable, not only from the USA, but all over the world. Depending on your current nameserver’s reliability, your results may vary. Use indeep76 to check or use a monitoring service like mon.itor.us or pingdom to give you a nice baseline. If you are getting anything close to 200ms + response times, then there is room for improvement. If you want to use Route 53 on your domain, then head over to dns30 and make sure to have your Amazon AWS API keys handy. It’s a simple setup and will make your site that much faster.
Sound like too much work for not enough payoff? Scared of changing nameservers and risking your site be unaccessible? I don’t blame you. However, I will say that if you are obsessed about page speed and have already optimized your site via gzip compression, minification, JS packing, and a CDN, then optimizing your DNS lookup time is your final step.