Designing persistence schema for BigTable on AppEngine

Posted by Vitalij Zadneprovskij on Programmers See other posts from Programmers or by Vitalij Zadneprovskij
Published on 2012-11-07T21:52:17Z Indexed on 2012/11/07 23:13 UTC
Read the original article Hit count: 428

Filed under:

database-design

|

relational-database

I have tried to design the datastore schema for a very small application. That schema would have been very simple, if not trivial, using a relational database with foreign keys, many-to-many relations, joins, etc.

But the problem was that my application was targeted for Google App Engine and I had to design for a database that was not relational. At the end I gave up.

Is there a book or an article that describes design principles for applications that are meant for such databases?

The books that I have found are about programming for App Engine and they don't spend many words about database design principles.

© Programmers or respective owner

Related posts about database-design

(Database Design - products attributes): What is better option for product attribute database design

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi, I new in database design. What is better option for product attribute database design for cms?(Please suggest other options also). option 1: 1 table products{ id product_name color price attribute_name1 attribute_value1 attribute_name2 attribute_value2 attribute_name3 attribute_value3 } option… >>> More
Book Review: Pro SQL Server 2008 Relational Database Design and Implementation

as seen on SQL Blog - Search for 'SQL Blog'
Investing in proper database design is a very efficient way to cut maintenance costs. If we expect a system to last, we need to make sure it has a good solid foundation - high quality database design. Surely we can and sometimes do cut corners and save on database design to get things done faster… >>> More
Advice on database design / SQL for retrieving data with chronological order

as seen on Stack Overflow - Search for 'Stack Overflow'
I am creating a database that will help keep track of which employees have been on a certain training course. I would like to get some guidance on the best way to design the database. Specifically, each employee must attend the training course each year and my database needs to keep a history of… >>> More
Fiscal year handling strategies in database design

as seen on Stack Overflow - Search for 'Stack Overflow'
By fiscal year I mean all the data in the database (in all tables) that occurred in the particular year. Lets say that we are building an application that allows user to choose from different years. What way of implementing this would you prefer, and why: Separate fiscal year data based on multiple… >>> More
Database design for summarized data

as seen on Stack Overflow - Search for 'Stack Overflow'
I have a new table I'm going to add to a bunch of other summarized data, basically to take some of the load off by calculating weekly avgs. My question is whether I would be better off with one model over the other. One model with days of the week as a column with an additional column for price… >>> More

Related posts about relational-database

Big Data – Buzz Words: Importance of Relational Database in Big Data World – Day 9 of 21

as seen on SQL Authority - Search for 'SQL Authority'
In yesterday’s blog post we learned what is HDFS. In this article we will take a quick look at the importance of the Relational Database in Big Data world. A Big Question? Here are a few questions I often received since the beginning of the Big Data Series - Does the relational database have… >>> More
SQL SERVER – Enumerations in Relational Database – Best Practice

as seen on SQL Authority - Search for 'SQL Authority'
Marko Parkkola This article has been submitted by Marko Parkkola, Data systems designer at Saarionen Oy, Finland. Marko is excellent developer and always thinking at next level. You can read his earlier comment which created very interesting discussion here: SQL SERVER- IF EXISTS(Select null from… >>> More
SQL SERVER Enumerations in Relational Database Best Practice

as seen on Dot net Slackers - Search for 'Dot net Slackers'
This article has been submitted by Marko Parkkola, Data systems designer at Saarionen Oy, Finland. Marko is excellent developer and always thinking at next level. You can read his earlier comment which created very interesting discussion here: SQL SERVER- IF EXISTS(Select null from table) vs IF EXISTS(Select… >>> More
Details of 5GB and 50GB SQL Azure databases have now been released, along with new price points

as seen on Geeks with Blogs - Search for 'Geeks with Blogs'
Like many others signed up to the Windows Azure Platform, I received an email overnight detailing the upcoming database size changes for SQL Azure. I know from our work with early adopters over the last 12 months that the 1GB and 10GB limits were sometimes seen as blockers, especially when migrating… >>> More
Are document-oriented databases meant to replace relational databases?

as seen on Stack Overflow - Search for 'Stack Overflow'
Recently I've been working a little with MongoDB and I have to say I really like it. However it is a completely different type of database then I am used. I've noticed that it is most definitely better for certain types of data, however for heavily normalized databases it might not be the best choice… >>> More