beau

I do gzip the streamed JSON. Try:

$ curl -H "Accept-Encoding: gzip" --trace - "https://instantdomainsearch.com/services/vanity/apple?hash=8...

I tried this a long time ago. At the time, certain queries were hard for a server to answer. Other clients connected to the zombie server stalled until something timed out. With HTTPS, a load balancer can direct new queries to servers that are responsive.

It's also easy to load them into Google's BigQuery: https://cloud.google.com/bigquery/docs/loading-data#supporte...

I made this choice because so many tools support newline-delimited text. A quick search showed that others (Twitter, eBay) made the same choice, so I went with the flow.

*Thank you for NSBlog, it's great!

Thanks!

curl is a streaming parser. Most tools know what to do with a newline.

It works for Twitter: https://developer.twitter.com/en/docs/tutorials/consuming-st...

It is a pragmatic choice. Most languages can consume newline-delimited text natively. Do you really think getline() is going away?

Everyone should be firing.

Instant Domain Search did. People visiting the site tend to be ready to buy a domain, and Go Daddy does an amazing job of converting that intent into an actual sale.

Most if Snipshot's users tended to use the tool to crop and apply filters to photos they posted to social networks. Whoops.

That's surprising. Network Solutions was caught doing something like this (http://domainnamewire.com/2008/01/08/network-solutions-faces...) but I've never seen any evidence that Go Daddy does anything like this. Blake Irving is a good man.

Looks like you need to request an SLA credit manually: https://support.google.com/cloud/contact/cloud_platform_sla

Details: https://cloud.google.com/compute/sla

It's hard to find an available .com. But that doesn't mean you can't get one: https://instantdomainsearch.com/aftermarket/

.com is dominant. Even domai.nr changed their name to domainr.com. Over 90% of users at https://instantdomainsearch.com/ buy .com names.

CloudFront charges about $600 per month for "Dedicated IP Custom SSL": http://aws.amazon.com/cloudfront/custom-ssl-domains/

CloudFront only has a couple dozen edge locations: https://aws.amazon.com/about-aws/globalinfrastructure/region...

The real beauty of this setup is that the app server is also geographically distributed, and the flexibility to do whatever you want like support SPDY.

Route 53 is convenient because it integrates nicely with other AWS resources.

In my experience building http://instantdomainsearch.com/ I found that the "slow" part was actually the network round-trip to the server. WebSockets don't make packets move across the network any faster. We came up with a way to select the closest/fastest server when you first visit the site:

http://instantdomainsearch.com/articles/faster_domain_name_s...

This works well, but I think I'll switch to Amazon's Route 53 (DNS) implementation now that it can do failover.

I've owned an electric car for about two years now. The article missed a few points:

1. The regenerative braking means you do not need to replace your brakes nearly as often. (Tires are a different story.)

2. There are far fewer moving parts than a normal car. This decreases the amount of maintenance you need to do.

3. Since there are no moving parts, it's less damaging to the car when drive it hard. Accelerating quickly with non-electric sports cars wears out very expensive components very quickly. With an electric car, you can get that 0-60 performance every single time you accelerate without wearing anything out. (Except the tires.)

When you're comparing the annual fuel bill to the extra cost of the Tesla, don't forget that you are buying a premium sports car. Something like a BMW M5 gets 14/20 MPG, and expects that you feed it premium fuel.

This is a great start. I built Instant Domain Search (IDS) almost 7 years ago, and have learnt a lot from the experience. Some quick thoughts:

1. There are no margins in the domain industry. Start thinking about building a hosting company. Your site is cool, but weebly.com and heroku.com are real businesses. I work full-time for Facebook, not IDS. (BTW, Facebook is hiring people like you, message me at http://www.facebook.com/beau if you're interested.)

2. It needs to be faster. For example, to squeeze another few hundred milliseconds out of our search, we built a distributed search infrastructure described here: http://instantdomainsearch.com/articles/faster_domain_name_s...

3. You should search names listed in the aftermarket and include them in your results. I've worked with http://www.buydomains.com/ for several years, and am happy with them. I can make an intro if you'd like.

4. Consider extracting words and doing a basic thesaurus search. We're doing something like that at http://instantdomainsearch.com/suggestions/

Hope this helps!

Yeah, I think the article should have a code sample.

I'm having a great time at Facebook.