wsh91
Joined 14 years ago
Karma
374
Submissions
106
Member since
Dec 31
[ my public key: https://keybase.io/wsh; my proof: https://keybase.io/wsh/sigs/TdNOlr9c_La5rnHvv39SN8ZIMDCBsCZ9LXzCOTu3EgE ]
View on Hacker NewsRecent submissions
Comment · 7 years ago
Hi there! One thing you might consider is using a function to replicate your Firestore data to BigQuery, depending on the value the latter would add. (Very fast OLAP; I'm a big fan.)
(Cloud Firestore eng. here.)
Comment · 7 years ago
Hi there. :) I'm an engineer on the Cloud Firestore team. I can't speak to if or when we'll be able to remove this restriction, but please know that the folks working on this (like me) are very aware of what a pain in the butt this is. I'm sorry that I can't give you a more satisfying answer, but I hope we'll be able to change this soon. Thanks for being a customer!
Comment · 7 years ago
Cloud Spanner is also relational. :)
(Fellow GCPer.)
Comment · 7 years ago
An export is one component of a backup solution. :) Scheduling is another (https://firebase.google.com/docs/firestore/solutions/schedul...). (Checking restores is critical, too; that's also feasible [managed import into a new cloud project] but requires a bit more legwork.)
(I work on Cloud Firestore.)
Comment · 8 years ago
Is there anything we could be doing to serve you better?
Comment · 8 years ago
a) Cloud Firestore supports transactions across the entire database. You can learn more about them here: https://cloud.google.com/firestore/docs/manage-data/transact....
b) Given that the primary use case for namespaces was/is multitenancy, it's not clear to me why you'd want to transact across them. Nevertheless, you can. What's leading you to draw this conclusion?
Comment · 8 years ago
Cloud Firestore (the next generation of Cloud Datastore) removes those limitations. https://cloud.google.com/firestore/docs/manage-data/transact...
It also supports the Cloud Datastore API.
(I work on it!)
Comment · 8 years ago
Hey there--I'm an engineer on the Cloud Datastore team. I'd love to know more about what your needs are if you're willing to share.
Comment · 8 years ago
This (fantastic) paper is cited in the Google Megastore paper [1] and we actually use the term "entity group" in our product [2] indirectly because of it. Pat Helland is always worth reading; thanks to the submitter for the reminder.
[1] https://static.googleusercontent.com/media/research.google.c...
[2] https://cloud.google.com/datastore/docs/articles/balancing-s...
Comment · 9 years ago
Have a look at https://cloud.google.com/compute/docs/load-balancing/ipv6.
(Disclaimer: I work on GCP, albeit not on networking stuff.)
Comment · 9 years ago
Only because this question has been asked multiple times at TGIF (regular all-hands meeting).
Comment · 9 years ago
That's not true. Anyone has access to 20% time, the question is just whether or not it makes sense for individual people.
Source: I work here and take advantage of 20% time.
Comment · 9 years ago
Heh. :)
One technicality: DynamoDB's pricing is based on throughput, as you know, but it's provisioned throughput. (You manage your capacity unit allocations yourself, at least that was the case a little while ago.) You're charged money for how much you provision regardless of whether or not you actually consume the capacity units. Our pricing model (like Fauna's) only takes ops and storage into consideration.
Comment · 9 years ago
I can't speak to the SDK parts, but take a look at Firebase's suite more broadly. :) Viz a viz Cognito, check out Authentication and the Realtime Database in particular.
Comment · 9 years ago
Firebase's Realtime Database does this, too.
https://firebase.google.com/pricing/
(Disclosure: I work on Cloud Datastore, which is another Google Cloud product; it, too, does pricing based on ops and storage rather than provisioning, as my colleagues note.)