Tue
Dec 1
2009
Four short links: 1 December 2009
Open Source Cinema Camera, Collaborative Filtering, Message Queue for Replication, Facebook Data Warehouse Numbers
by Nat Torkington | @gnat | comments: 6
- Apertus -- open source cinema camera. (via joshua on Delicious)
- A Survey of Collaborative Filtering Techniques -- From basic techniques to the state-of-the-art, we attempt to present a comprehensive survey for CF techniques, which can be served as a roadmap for research and practice in this area. (via bos on Delicious)
- Drizzle Replication using RabbitMQ as Transport -- we're watching the growing use of message queues in web software, and here's an interesting application. (via sogrady on Delicious)
- Facebook Data Team: Distributed Data Analysis at Facebook -- job ad from Facebook gives numbers on company use of their Hive data warehouse tool built on top of Hadoop: Today, Facebook counts 29% of its employees (and growing!) as Hive users. More than half (51%) of those users are outside of Engineering. They come from distinct groups like User Operations, Sales, Human Resources, and Finance. Many of them had never used a database before working here. Thanks to Hive, they are now all data ninjas who are able to move fast and make great decisions with data. (via Simon Willison)
tags: collective intelligence, data mining, facebook, hadoop, hardware, media, message queues, mysql facebook, opensource
| comments: 6
submit: 
0 TrackBacks
TrackBack URL for this entry: http://blogs.oreilly.com/cgi-bin/mt/mt-t.cgi/10051
Comments: 6
you've fixed the title, but you might
want to also fix the u.r.l., or your
archives will be mightily messed up.
-bowerbird
@bowerbird - if we do, we bugger any inbound links and lose the googlejuice. Easier to just let it sit as a reminder to me to pay more attention at the start of the month :)
you've fixed the title, but you might
want to also fix the u.r.l., or your
archives will be mightily messed up.
-bowerbird
sorry for the repost. i was looking at
an unrefreshed version of the page...
there are any number of ways that
you could reroute the inbound links
so as to have a _new_and_correct_
u.r.l. assigned to the post, and then
your archives and indexes wouldn't
continue to propagate your error...
i've seen this issue from both sides,
and believe me, the future confusion
goes on for a very long time, so you
really want to fix this while you can.
a word to the wise is sufficient.
-bowerbird
Post A Comment:
STAY CONNECTED
RECOMMENDED FOR YOU
O'Reilly Tools of Change for Publishing Conference, February 22 - 24, 2010, New York, NY
Where 2.0 Conference, March 30 - April 1, 2010, San Jose, CA
O'Reilly MySQL Conference & Expo, April 12 - 15, 2010, Santa Clara, CA
Web 2.0 Expo, May 3 - 6, 2010, San Francisco, CA
Gov 2.0 Expo, May 25 - 27, 2010, Washington, DC
$249.00Twitter and the Micro-Messaging Revolution, OReilly Radar Report
RECENT COMMENTS
- bowerbird on Four short links: 1 December 2009: sorry for the repost. ...
- bowerbird on Four short links: 1 December 2009: you've fixed the title,...
- gnat on Four short links: 1 December 2009: @bowerbird - if we do, ...
- bowerbird on Four short links: 1 December 2009: you've fixed the title,...
- Ahmadism on Four short links: 1 December 2009: The title of today's po...
- Billy Mumford on Four short links: 1 December 2009: Uh, it's *December*....
RADAR TOPICS
Billy Mumford [2009-12-01 09:08 AM]
Uh, it's *December*.