Replace Firebase/Firstore with something better #27
Comments
|
If you want slightly better queryability, but also the real time factor, have a look at the new Cloud Firestore |
|
I've been using Firestore, since (legacy?) Firebase was pretty horrible to use for ordered lists. |
|
I see. (It's called the Firebase realtime database). Yeah, they are both
quite limited!
…On Mon, Jan 1, 2018, 9:17 AM Brian Vaughn ***@***.***> wrote:
I've been using Firestore, since (legacy?) Firebase was pretty horrible to
use for ordered lists.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAR4jJUqkDwL4ZjcYlxedtT16JNMOY0cks5tGIaagaJpZM4RP_cS>
.
|
|
Thanks for the pointer though! I appreciate the thought. Invested a decent amount of energy trying to get Fire* working for this project but it still feels...limited, awkward, and unintuitive to me. Oh well. 😄 Happy New Year buddy. |
|
You too!
…On Mon, Jan 1, 2018, 9:27 AM Brian Vaughn ***@***.***> wrote:
Thanks for the pointer though! I appreciate the thought.
Invested a decent amount of energy trying to get Fire* working for this
project but it still feels...limited, awkward, and unintuitive to me.
Oh well. :Smile:
Happy New Year buddy.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#27 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAR4jBPGF7g_VlneIz7f1lIzJ8AZcWbOks5tGIjrgaJpZM4RP_cS>
.
|
bvaughn
changed the title
|
Added download/export option via #7 to support some kind of migration from Firebase to something else. |
|
Was thinking to myself that maybe it would be nice to support a couple of backends. I'm not thrilled with Firestore, but at least it works (if you overlook hacks like this). Maybe it would be possible to make an interface for Maybe users could select which one to use before signing in (if we bundle-split) or maybe we could make it a build-time step. This would be more work, and it might not be worth doing- particularly if certain backends support features that others don't. It's just a thought. |
|
I think I've run out of patience with Graph.cool, unfortunately. The docs seems to be wrong in so many places- either outdated (referencing functions/libs that don't exist anymore) or the code they show in the tutorial fails when run in the Playground, etc... It looks like a nice service in many ways, although the auth example is pretty heavy on the boilerplate. I just don't have the time or patience to sort through the docs at the moment, since this is a side project. |
|
I also got this error while being the sole user of an app with at most 1 insert per second from the server.
Firestore is still in beta, and writes are capped to 1 per document per second, so that might have triggered the error. |
|
This warning just means that you guys have maxed out your free daily quota of reads and writes, you either need to bump up to a paid plan or wait a day for the quotas to be restored. |
|
Yeah, but as the issue description mentioned- the traffic/load for this app was super minimal to have already bumped up against the free tier limit. 😊 |
|
It's not just traffic. There are a whole host of things that you could've maxed out if you're using apis, cloud functions, storage, etc. If you check the usage tab on firestore/rtdb next time it happens it will take you to a dashboard that shows you exactly what maxed out. |
|
I was using the word "traffic" very broadly to mean reads and writes. The amount of data actually stored by this app is very small. But good suggestion, thanks for mentioning the usage tab. 😊 |
|
|
Is there a limit on Cloud messages as well ? I cant find any documentation on the quota of messages. |
In general, I've found Firebase to be awkward to work with- from authentication to querying.
Its support for compound queries is very limited. For example, it doesn't support logical OR or the "!=" operator, pushing the burden onto the client.
Its authentication model feels awkward too: Sessions aren't persisted between page reloads for some providers (eg Google). I was unable to get Facebook to actually work. etc.
Then tonight while testing the new summary page, I started seeing this error:
This app has experienced very light traffic, so the above message is concerning.
Anyway, all of the Firebase-specific code is abstracted away behind
DataStoreso in theory, it should be easy enough to remove.I asked for recommendations about this on Twitter some time ago, and based on the responses I got, Graph.cool seems like a good option to consider. This article compares GraphQL to Firebase and touches on some of the pain points mentioned above (like limited querying). Another possibility is AWS AppSync.
The text was updated successfully, but these errors were encountered: