5 ms·

Yahoo's Cloud

• deleted 17y ago
  [deleted]
• Tichy 17y ago
  What's up with the "value" String in this example? "addr":{"value":"700 First Ave"}
  • timtrueman 17y ago
    It's the address of Yahoo!'s headquarters. (edit: yeah I don't know why I didn't see what thwarted saw, clearly I'm an idiot)
    • thwarted 17y ago
      I think the question is why isn't it: {"addr":"700 First Ave"}
      • jm4 17y ago
        This is just a stab in the dark but the other method would allow for metadata on individual fields, although I can't think of what kind of metadata you'd want to add to a street address.
        • DenisM 17y ago
          I think the primary purpose is to annotate values with type information to make the format self-describing.
        • johnxorz 17y ago
          You could have versioning information, expiry time, or type information for the field.
      • michi009 17y ago
        Sherpa supports field expiry. {"addr": {"value : "700 First Ave", "expiretime" : 1244146191 }}
• pierrefar 17y ago
  This looks really cool. I really hope they expose it as an API or even better release it with a permissible license for us to deploy. We need aggressive competition against SimpleDB and the large number of key-value stores we already have.
• jrnkntl 17y ago
  One day I hope for more universal cloud api's so that switching between services or distributing it (if ever needed ;)) over different cloud service providers doesn't require rewrites or extra overhead. idea, write some Cloud Service Communicator API that connects through all other api's. Another layer to add.
• swaroop 17y ago
  Shouldn't the title be "Yahoo's cloud database"... I was almost expecting another EC2.
• farnulfo 17y ago
  A bit of vaporware here. No plan to quickly open this service.
  • DenisM 17y ago
    Is GFS vaporware? It is closed to public.
• joshu 17y ago
  I was waiting for something like this forever and ever when I worked there.
  • aristus 17y ago
    It already existed, kinda. When I was there I built a library called CrockDB that squirreled small values into the Calendar API, which runs on UDB or something. A part of the key was a unixtime so I always made sure Crock stored its stuff in the 14th century so as not to conflict with real user data. :)
    • joshu 17y ago
      Yeah, I don't think we could have gotten away with storing delicious bookmarks in UDB...
• marcua 17y ago
  In case you're wondering, the paper and technology that this is based on is here: http://research.yahoo.com/node/2304 http://research.yahoo.com/node/2304