Google Firebase Reviews

We use the solution for user management.

The solution is useful for managing users and user authentication.

We had some compatibility issues with Elixir. It had some library compatibility issues. We did a workaround through Google Cloud Functions and achieved the desired output.

I have been using the solution for the last four years.

I rate the tool’s stability a ten out of ten.

I rate the tool’s scalability a ten out of ten. In the past, we had 70,000 users. The usage was reduced later.

The initial setup is simple. The solution is cloud-based.

I rate the pricing a five out of ten.

Overall, I rate the tool a ten out of ten.

We use Firebase as a proof of concept to introduce Apogee functionality in the future. We need to simulate some scenarios using Apogee as a lesson for API management and Firebase is the backend database we use to simulate custom scenarios regarding the customer needs.

We use the public cloud version.

I found the flexibility of handling and dealing with the database through EDL to be very useful.

Their technical support needs to be enhanced with more support for customers.

They should also improve the monitoring and control for the database to monitor the performance and fine-tuning of the database itself. Automatic detection of potential errors or failures in the database would also be very helpful. For example, I would like to receive notifications for the admin to take appropriate action for database failures.

Deployment and maintenance requires two or three people for us.

I think it's a rich community, but they should increase the line support of technical issues and get official support to users or customers for Firebase so they can get their answers quickly. Most questions can be answered from the history of other questions and there is a community for all these questions and answers, which helps newcomers to with deployment and maintenance of the Firebase Database.

I was mainly using Oracle Database, which has different concepts for different scenarios, to some extent. Since it's one year old, it's tough to move to the Firebase Database.

I have had a good experience in both Google and Oracle environments and I also have had good experiences in Google constantly, which is a cloud environment, in which you can build a private cloud environment.

The initial setup was straightforward. It took around two or three hours.

I would rate Firebase as eight out of ten.

We use Firebase on-premise. Our primary use cases are for push notifications and for realtime chat.

I'm really happy with the performance and with what it gives us. 

The most valuable feature I like is that it is in realtime. Updates are also very fast. 

We use Firebase for media processing and we are growing more. As we grow, the pricing goes up and it's high compared to competitors. The solution is expensive. 

In the next release, they should focus more on realtime features. 

It's stable. Stability and the performance are really good.

We have plans to expand it across the organization. 

I never had to contact their technical support. 

Licensing costs are on a monthly basis. 

I would rate it a seven and a half out of ten. Not a ten because I haven't explored every facet to it. I am very happy with what I have seen so far. 

Google Firebase helps us build and run applications.

The solution could improve by providing an improved SDK tool and automatic indexing for databases.

I have been using Google Firebase for approximately four years.

The solution is stable.

Google Firebase is scalable.

The price of Google Firebase is very good.

I would recommend this solution to others.

I rate Google Firebase a nine out of ten.

The primary use case is the documentation.

Firebase is awesome and easy to use. It is a database without any schema from the client-side. Additionally, it has security rules to control database read/write operations in real-time.

• Information stored in the cloud and readily available everywhere.
• The big power of their the data host.

Firebase uses JSON, and the storage format is very different to that of SQL. This does not allow for easy migrations.

The support team is responsive and well-informed.