I'm a big fan of services like Parse & Firebase so it's cool to see something open source and independent get released.
I've never made the jump to use Parse or Firebase in production though because inevitably I have to write some custom server code to do some integration. For example - payments with Stripe. Charges should only occur on your server (not on the client) but I've yet to see anyone allow you to configure a payment trigger in one of these services.
Basically, you need a service running on a separate server to implement these sorts of integrations. If Firebase is a long-term part of your stack, I agree that sounds unappealing, b/c the reason you're paying Firebase is so you don't need to wrangle a server.
You may think differently if you're using Firebase as the fastest way to get an MVP up and running (that happens to be my use case)
Of course you can use firebase also in combination with server side code. It is no reason not to use firebase because you use server side code.
I use firebase and SQL at the same time. It works quite good if you know what you do.
Comments
I'm a big fan of services like Parse & Firebase so it's cool to see something open source and independent get released.
I've never made the jump to use Parse or Firebase in production though because inevitably I have to write some custom server code to do some integration. For example - payments with Stripe. Charges should only occur on your server (not on the client) but I've yet to see anyone allow you to configure a payment trigger in one of these services.
Basically, you need a service running on a separate server to implement these sorts of integrations. If Firebase is a long-term part of your stack, I agree that sounds unappealing, b/c the reason you're paying Firebase is so you don't need to wrangle a server.
You may think differently if you're using Firebase as the fastest way to get an MVP up and running (that happens to be my use case)
We use parse with stripe. The client drives the transaction and then stripe hits your parse cloud function via webhook with the confirmation.
Of course you can use firebase also in combination with server side code. It is no reason not to use firebase because you use server side code. I use firebase and SQL at the same time. It works quite good if you know what you do.
I've done exactly that - integrated Stripe with our Firebase-backed app (https://play.google.com/store/apps/details?id=com.twansoftwa...). My method was to use App Engine as the callback component to handle Stripe webhooks.
I also do have custom server code, which was a little bit tough to get going, but it's great having a dedicated Linux box as well.