What if we made a storage engine that used MogileFS to store blobs/images?

I’m happy to release version 0.1 of the NDB/Python bindings. They are very young and not very well documented yet, but email me if you are interested in them and especially if you are interested in helping out. I’ll get a Trac system up and going (or something) or maybe sourceforge or savannah or google code or you know, whatever.

python-ndbapi-0.1.tar.bz2

Welcome to the 18th Log Buffer, the weekly human-edited review of news from database blogs. There’s no shortage of conferences and news about them, so let’s have a couple items on UK Oracle User Group Conference & Exhibition (UKOUG) to start. The titular Doug Burns of Doug’s Oracle Blog posts his personal agenda for the UKOUG. [...]

This are the steps to setup a brand new installation of OS X Server Tiger. This is for an "all in one" server typical for a small or startup WebObjects website or as a server used for testing. This setup is for MySQL 4.1, WebObjects 5.3, Apache webserver. The mechanics of WebObjects setup on a new installation of OS X Tiger is straight-forward and easier than with previous versions of OS X Server.

I’m outside enjoying a very lovely Danish and Orange juice with Jay and Leslie, and like 3 motorised scooters and a guy on a skateboard goes past. Did I mention how cool this place is!

Back in the foyer and Sheeri is sitting in the leather massage chair, as more people start streaming in. She has her laptop there and is IM’ing her boyfriend.

“So I’m in a massage chair at Google head quarters”. And his response is , “like right now”. Well here will be the photo and video when we find somebody with a card reader for my camera.

Jay’s looking a little worried, registrations are now over 200, 202, yesterday is was 150, and like 3 days ago, still in the 70s & 80s. People must have found out a free event at MySQL. We are going to kick people out that don’t contribute. It is a unconference.

So now that I write this, registrations are at 206.

So like two minutes later, some official looking Google people come over and saw “Come on over and get your Google Shirt”. So before the last past is even cold, we have our own Googlewear.

A minute later, Leslie is back again saying, guys and lady (Just for Sheeri), “Contintental breakfast is ready in the room”. Now to check out the Google Food!

Everybody here (that is not us visitors) are wearing Google shirts. It must be an official clothing label.

So Sheeri says “Actually they are just extras, they have been hired for the day.”

So the latest quote from Leslie is “Eat, joy and be merry, and stay inside the blue lines”. Of course I should also mention when we arrived the parking security guy said. “Follow the second yellow brick road”. This is going to be a weekend just of quotes!

We have made it to MySQL Camp being held at Google Head Quarters in Mountain View California. Directions WOOT!!!

So we are at the lobby reception of Building 40, and I’m lounging back in a large green beanbag behind all the name tags, this is so cool, the problem is with all our technology, nobody yet has the capability to read the photos from a digital camera so I can upload it. Both Sheeri and myself have left the right stuff in our hotel room. So stay tuned.

Leslie our Google co-coordinator wants her business card to read “Hacker Herder” which sounds so cool. This whole weekend is going to be a blast. More to come.

What I have been thinking about is how to grow a caching system. I
want to be able to start out with something small, that I can use on
a small scale, and then move to a larger system as needed. Some
requirements:

1) I don't want to rewrite everything as I grow the system.
2) I want an interface which gives me the ability to store
attributes, with a preference to being able to look at those without
de-serializing an objects.
3) Geographical redundancy. If the entire network falls apart I want
to able to bring the system up elsewhere with only a single step
"backwards" for cached data. I can handle a little bit of stale data,
but I don't want it to be greater then an hour old.
4) I want to be able to run analytics on state information.
5) KISS, Keep it simple.

Today this is the most common design:

…

Leonard Richardson and Sam Ruby are writing a book about web services and REST. They see superficial bloat in the way web services are built today. In short, they say to build a web page, you only need to know HTTP and HTML but to build Web Service a huge load of technologies has to be integrated:

XML, SOAP, WSDL, UDDI, WS-Policy, WS-Security, WS-Eventing, WS-Reliability, WS-Coordination, WS-Transaction, WS-Notification, WS-BaseNotification, WS-Topics, WS-Transfer

From a conceptual point of view, web pages appear to be the modest, hard-working older brother of the good-looking blabbermouth web services. How come?

REST defines web services with the tools of web pages—HTTP and URIs. Those who claim that this won't scale the book simply asks why the web scales when it is based on the same tools?—Touché.

With REST every resource has …