On Mon, Jun 9, 2014 at 3:20 AM, Mark Cummins <[email protected]> wrote:
> Hi Andrew, > > Nice to hear that naked domains are now supported too. Given a free > choice, is there any reason to prefer www.example.com over example.com? > I'm new to the issue and just noticed some other providers advise against > naked domains for scalability reasons: e.g.: > https://devcenter.heroku.com/articles/apex-domains > > Or is this not a concern on App Engine? > I'm not Andrew, but I'll throw my $0.02 in: It's not only a scalability issue, but it's also a fault-tolerance issue. As the article notes, CNAMEs are easier to change if an issue occurs: the route to your site can be modified quickly, which results in higher uptime. But there are also other issues, such as cookies: cookies set using a naked domain are sent to all subdomains, which can be annoying if you decide to add a static content subdomain: to fully optimize page speed, it's better if cookies are not sent to or from static asset domains/subdomains. Plus, a www subdomain is nicer from an UX perspective: it's easier later to break up your site into separate sections such as blog.example.com, news.example.com, api.example.com, etc. But if you're not concerned about expanding later or cookies, there's nothing inherently wrong with using a naked domain. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
