42 ms·
If by "proper database layer" you mean a relational DBMS then: First go read the responses to the article "Maybe Normalizing Isn't Normal" at http://www.coding
by giardini 18y ago
If by "proper database layer" you mean a relational DBMS then:
First go read the responses to the article "Maybe Normalizing Isn't Normal" at http://www.codinghorror.com/blog/archives/001152.html http://www.codinghorror.com/blog/archives/001152.html which should convince you to normalize your database.
Secondly peruse the Google App Engine newsgroup at http://groups.google.com/group/google-appengine http://groups.google.com/group/google-appengine
wherein much ado is made about how normalization is a _bad_ thing for Google App Engine databases.
Finally choose: do you want a consistent database or a very, very fast database that may be inconsistent?
I chose consistency and consequently abandoned the idea of using Google App Engine. I gain further peace of mind by _not_ abandoning decades of relational database wisdom.
Google isn't infallible.