Firebase vs. Google Compute Engine

Firebase should be your first choice if your platform is mobile first. Firebase's mobile platform support for client-side applications is second to none, and I cannot think of a comparable cross-platform toolkit. Firebase also integrates well with your server-side solution, meaning that you can plug Firebase into your existing app architecture with minimal effort.

Firebase lags behind on the desktop, however. Although macOS support is rapidly catching up, full Windows support is a glaring omission for most Firebase features. This means that if your platform targets Windows, you will need to implement the client functionality manually using Firebase's web APIs and wrappers, or look for another solution.

Incentivized

It is excellent if you have any workloads that need raw computing or plan to have any state-full services running in your environment like DBs (for which you don't want to use Managed services), cache, etc. It also gives you complete control over which versions of software, OS, etc., you need, and thus, you can build anything and deploy it on GCE.

Incentivized

• Extremely robust. Has about any tool you can think of under one roof making it extremely useful as a backup platform for data analytics or small teams that need something quickly.
• Intuitive and easy UI/UX. Being made and owned by Google, you expect nothing less. Very easy to use for anyone that has any marketing or analytical experience especially in Google Analytics (which I just assume all marketers do).
• Safe, secure, and sturdy. Never need to worry about downtimes or misinformation as it's as clean and safe as it is being run by Google.
• FREE! What else is there to say. Unless you're an extremely large application handling hundreds of thousands to millions of users, this pay as you go plan will stay free.

Incentivized

• A simple web-based interface that is a breeze to train new engineers to use. Our experienced engineers never have trouble finding or doing anything on GCE.
• Sustained use and Committed use discounts mean we get top-tier VMs for an incredibly competitive price.
• Wonderful identity and access management that gives us peace-of-mind when granting access to machines to contractors and other 3rd parties.
• Fast VMs, lastest in hardware, and enough RAM to power even the hungriest of our services.

Incentivized

• Firebase/Firestore has very limited support for querying more complicated items; for example, performing a simple string search is not possible.
• While upfront costs are low, costs can grow quickly if you're not careful about what you are being billed for.
• Dashboards have at times shown different information to what is billed, and support from Google is less than stellar and not as effective as that from Amazon or Microsoft.

Incentivized

• The L7 load balancer can be difficult to get set up. It's limited in its functionality, especially with the container engine.
• It's hard to find certain objects on the web console. Often times the things I need to get to are buried in advanced menus.
• Google's decision to only support MySQL on their relational DB service means that I have to manage Postgres instances in Compute on my own, managing everything from storage to backups.

Incentivized

Its pretty good, easy and good performance. Also, interface is very good for starters compared to competitors. Infra as Code (IaC) using Terraform even added easiness for creation, management and deletion of compute Virtual Machines (VM). Overall, very good and very easy cloud based compute platform which simplified infrastructure, very much recommend.

Incentivized

I don't use the Firebase UI much, but rather connect it to GA4. GA4 has a great event model but the GA4 UI and analysis capabilities are limited. It's harder to measure product usage type of engagement but if you have the time and resources to leverage the GA4 to BiqQuery export you'll have all the raw event data you'll need for deep analysis, segmentation, and audience activation.

Incentivized

Having interacted with several cloud services, GCE stands out to me as more usable than most. The naming and locating of features is a little more intuitive than most I've interacted with, and hinting is also quite helpful. Getting staff up to speed has proven to be overall less painful than others.

Incentivized

Google Compute Engine works well for cloud project with lesser geographical audience. It sometimes gives error while everything is set up perfectly. We also keep on check any updates available because that's one reason of site getting down. Google Compute Engine is ultimately a top solution to build an app and publish it online within a few minutes

Incentivized

Google Compute Engine usually delivers good and predictable performance for our self-hosted stack of applications. However, when running n8n heavy workflows, even with a tunned instance configuration in docker, performance usually peaks usually due to memory usage. We often need to upgrade memory when we have heavier data processing and workflows. Other than that, in a normal usage, we don't really have any problems

Incentivized

Our analytics folks handled the majority of the communication when it came to customer service, but as far as I was aware, the support we got was pretty good. When we had an issue, we were able to reach out and get support in a timely fashion. Firebase was easy to reach and reasonably available to assist when needed.

Incentivized

• The documentation needs to be better for intermediate users - There are first steps that one can easily follow, but after that, the documentation is often spotty or not in a form where one can follow the steps and accomplish the task. Also, the documentation and the product often go out of sync, where the commands from the documentation do not work with the current version of the product.
• Google support was great and their presence on site was very helpful in dealing with various issues.

Incentivized

Before using Firebase, we exclusively used self hosted database services. Using Firebase has allowed us to reduce reliance on single points of failure and systems that are difficult to scale. Additionally, Firebase is much easier to set up and use than any sort of self hosted database. This simplicity has allowed us to try features that we might not have based on the amount of work they required in the past.

Incentivized

When configuring Amazon ECS, it is a bit confusing as you are not able to find the actual issue. You need to enable Additional AppInsights to get detailed level info, which is not a concern when configuring on the Instance Level. Moreover, Azure VM does not provide an in-browser option; instead, it is Azure Bastion, but for that, you have to enable a dedicated subnet, which is a bit unnecessary.

Incentivized

It works really well with other Google Cloud services, making it easy to build scalable solutions across different teams and locations.

Incentivized

• Firebase has been able to help us understand reliably, the drop-off in our user flows with their funnel feature. This has made it easy for us to be able to pinpoint weaknesses in our funnel and test and optimize with data as the dependent variable.
• From an economic standpoint, we don't pay for Firebase which is great, but as the saying goes "You get what you pay for" also holds true in this context. As we looked to grow and scale, we looked for a paid solution.
• From a developer resource standpoint, Firebase has been extremely easy to integrate into our app. Whether it be the event tracking, dynamic links or crash reporting we have not had to waste too much developer time thanks to their well-organized developer docs.

Incentivized

• Scalability means flexibility and less upfront costs
• Can become expensive when hard set compute requirements are clear, but things like Spot VMs can help here too, or just having your own infrastructure and scaling up with Google. This is for more advanced cases though
• Ramp up time is long, but after that it is quick to do many things and ROI is awesome

Incentivized