> "Because you must order based on the first filter in the where clause! Now, that's an important restriction when you're dealing with a petabyte of information

> "Because you must order based on the first filter in the where clause! Now, that's an important restriction when you're dealing with a petabyte of information." If you're dealing with queries on a petabyte of information, you'd likely have to deal with a number of issues, whether sharding, managing clusters of DB servers, etc. Sure, you have to structure your queries differently if you use Google's datastore but it's a trade-off. Being forced to think about scale-friendly coding isn't necessarily a bad thing. > "the datastore isn't flexible" I think you mean the datastore doesn't support the full spectrum of queries you expect from relational DBs. You can add new properties on-the-fly, so the schemas are extremely flexible in that regard. Just throw data at your datastore.