Google I/O 2008 - App Engine Datastore Under the Covers

Under the Covers of the Google App Engine Datastore
Ryan Barrett (Google)

Ever wonder why you can't do joins in the Google App Engine datastore? Why your app is seeing deadlines so often? Why it's so hard to tell whether a query will need an index? Why we offer both parent/child relationships and reference properties? Or why list properties don't seem to make any sense at all? This talk will explain how the datastore itself works, why these seeming peculiarities (and many others!) exist, and what you can do about them.

Category:

Science & Technology

Tags:

• Google
• I/O
• IO2008
• App
• Engine
• Datastore
• gcvio052008
• plid6D9B701069B4F2F4

[putinsays]

He is a such brogrammer :)

[GabRoyer]

@pcbdev No, the index only stores the key to the datas IIRC. Good question though

[pcbdev]

A (propably not so) stupid question ... If I'm going to write an application which stores e.g. data in 10 columns and my web-application supports sorting of all columns (as it is standard for lots of applications), does google have to store all my data in every sorting in their bigtable?

Is this then really 10 times my original data they have to store?

[MetzMy]

You can try being a little bit more open in expressing technical stuff, not just theory

[mboyemanster]

less "ums" please

[MrSwanson2008]

I'm interested in the datastore. Who cares what you think about presentation style?!

[drhannson]

Maybe something like this:

ManyToMany(dbModel): ref1 = ReferenceProperty()  ref2 = ReferenceProperty()

[kbghost]

still not 100% sure on how to design many-to-many relationships in the datastore

[kbghost]

still not 100% sure on how to design many-to-many realtionships in the datastore...