On the downside it can't do aggregates, it can't do query filters on more than one property, it can't do joins, it has its own unique query language, and it is a proprietary system with no chance of moving to another provider or hosting it yourself.
Speaking of it having its own query language, perhaps that isn't a big deal given you can't do any non-trivial queries.
For me, the pejorative NoSQL claim is actually a marketing turn off.
Comments
This looks pretty cool.
On the downside it can't do aggregates, it can't do query filters on more than one property, it can't do joins, it has its own unique query language, and it is a proprietary system with no chance of moving to another provider or hosting it yourself.
Speaking of it having its own query language, perhaps that isn't a big deal given you can't do any non-trivial queries.
For me, the pejorative NoSQL claim is actually a marketing turn off.
You can do query equality filters on more than one property using composite filters: https://developers.google.com/datastore/docs/concepts/querie... and composite indexes definition: https://developers.google.com/datastore/docs/tools/indexconf...