Four short links: 1 December 2009

Open Source Cinema Camera, Collaborative Filtering, Message Queue for Replication, Facebook Data Warehouse Numbers

  1. Apertus — open source cinema camera. (via joshua on Delicious)
  2. A Survey of Collaborative Filtering TechniquesFrom 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)
  3. 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)
  4. 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: , , , , , ,
  • Billy Mumford

    Uh, it’s *December*.

  • http://www.ahmadism.com Ahmadism

    The title of today’s post is a month behind.

  • bowerbird

    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

  • gnat

    @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 :)

  • bowerbird

    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

    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