advertise
« Strategy: Use Spare Region Capacity to Survive Availability Zone Failures | Main | Prismatic Update: Machine Learning on Documents and Users »
Thursday
Aug022012

Ask DuckDuckGo: Is there Anything you Want to Know About DDG?

Next week I'm going to have the pleasure of interviewing Gabriel Weinberg, founder of rebel search engine DuckDuckGo. Is there anything you would like to know about DuckDuckGo that I can ask Gabe? Please contact me or comment on this thread with your deepest desires.

Reader Comments (7)

I would be interested in:

- Frontend Tech Stack
- Backend storage/index architecture
- latency mgmt
- initial scaling challenge


well everything really .. :P

August 2, 2012 | Unregistered Commenterlambda

I would be curious to know what his strategy would be should Yahoo shut down Boss and Bing shut down their API.

August 2, 2012 | Unregistered CommenterSomeone

addition to above questions I would like to know business mode and revenue source?

August 3, 2012 | Unregistered CommenterSandy

Something about the Machine Learning (if any) they are using

August 4, 2012 | Unregistered CommenterLordDoskias

I'd love to hear how DDG plans on differentiating themselves from Google in the long run. How will they innovate the search process? And also, what do they think Google/Bing are currently doing wrong?

August 5, 2012 | Unregistered CommenterJordan

I second the revenue info. I use DDG all the time now as I value the privacy, but it does worry me that I see no obvious revenue stream.

August 6, 2012 | Unregistered CommenterChris Cowley

* Did they build their own crawler?
* Do they manage their own servers?
* What's their biggest limiting factor (in scaling)?
* What was their most stressful/challenging scaling/devops moment?

August 8, 2012 | Unregistered CommenterNick

PostPost a New Comment

Enter your information below to add a new comment.
Author Email (optional):
Author URL (optional):
Post:
 
Some HTML allowed: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>