Blog posts tagged "fluffy clouds"
April 17, 2009⇒ #2 Every Building with a Shoebox in it’s Basement.
“Buildings could offer WiFi photo uploading service, in return for keeping the photos taken of them….… what if Cloudgate were built with servers and wireless inside, right from the start, offering to consume the photos taken of it. You take a shot with a wireless enabled camera and it could store a copy for you. It’s building up a library of itself, in all seasons, in all weather. Meanwhile you, have a backup, findable by time and browsing, stored safely in the Cloud!”0. (Aside data, flickr, fluffy clouds, new cities, photography)
April 25, 2008⇒ random($foo): Internet Asshattery, Armchair Scaling Experts Edition.
I miss Leonard, Gordon, and Andy. But now that they’ve dispersed from Big Purple it’s nice to see all three of them schooling the internet in what real tech reporting might look like. You almost forget how bad it’s gotten until you see someone with a clue do it. Talk about amateur hour being over.0. (Aside fluffy clouds, lhl, reporting, scaling, social networks, techcrunch, twitter, upcoming)
April 20, 2008⇒ Hypertable looks really interesting from everything I’ve read but ….
… I can’t get over this nagging question, “Why does Zvents need a distributed, sparse matrix, versioned datastore?” I don’t track the calendaring space as much as I used to, and sometimes innovation is self justifying, but I’d feel a lot better about the project if I knew that answer.2. (Aside bigtable, calendaring, dist, fluffy clouds, hypertable, zvents)
Thinking again about distributed log oriented writes as a better architecture for a whole class of persistent data we need to deal with. Atomic appends are actually one of the least appreciated features in GFS, and certainly the most critical feature HDFS is missing. Right now I’m not even sure I’m supposed to be worrying, my back of the napkins are saying maybe 10-20mil daily appends across 3-4mil queues is just like running a big mail install right? (remind me to look at Maildir again)
Also contrary to TC’s breathy article BigTable is not much like SimpleDB (other then they’re both ways of storing and retrieving data which aren’t MySQL) in that it doesn’t give you querying, just limited range scans on rows, and it seems to be really really expensive to add new columns (at least whenever I talk to Gengineers, they seem to flinch at the concept)
Meanwhile I’m still waiting on DevPay for SimpleDB, before I get into it in a big big way.
February 19, 2008⇒ Amazon Developer Connection: Why S3 Failed.
The authentication cluster was overloaded, and improperly monitored. Complex systems are like that, never know where the problems will arise. Good clear communication, but it should have been on the AWS blog.0. (Aside, Uncategorized amazon, aws, communication, fluffy clouds, s3, transparency)
December 14, 2007⇒ Amazon.com: SimpleDB.
Building the Cloud Castle(tm), one brick at a time. Very similar set of operations to CouchDb, but without Couch’s views. Nice SimpleDB vs CouchDb side by side comparison. And more info from someone whose been playing with it longer.0. (Aside, Uncategorized amazon, aws, cloud, couchdb, fluffy clouds, simpledb)
Thinking about what “personal data stores” are going to look like, how this interacts with decentralized models for community services, (I swear I’ve written something more recent then 2005 on that topic, but can’t find it), mulling models for updating clouds, wondering if projects like G’s OpenSocial, and Portable Social Networks are a step forward or back, speculating that digital curation is a viable near future business model, and that individual curations would work well as shareable social media objects.
Nothing necessarily novel. Just where my head is at.
Only the barest of glances at Dynamo so far, and by far the most interesting pieces are going to be how they do the scalable high availability, and of course we’re talking about “Werner Vogels Scalability(tm)“, but I was immediately struck, [as Sam was](http://intertwingly.net/blog/2007/10/03/Key-Data ), by the this pattern key+data we’re seeing:
- memcached (everybody is using it)
- CouchDb (everybody is talking about it)
- Berkely DB (Bloglines and Yahoo to name just two, plus Google, thanks Steve)
- Facebook Data Store API
- and now Dynamo.
Meanwhile Assaf argues well that not all keys are created equal
Uploaded by joshua of california on 2 May 06, 6.19PM PDT.
But if you read it closer you’ll notice the operations map to what can de done in memcache (down to transactions are handled via atomic auto-increments) with a bit of cleverness, and some persistence. (pun intended) Still a nice step towards making developing f.bk apps a bit less eye-pokey-outty
Everyone is building the giant hash table in the clouds.