7 ms·
> firebase at google is doing extremely well Source? It's certainly popular but everyone I know (me included) is running away from it asap.
by pier25 7y ago
> firebase at google is doing extremely well
Source?
It's certainly popular but everyone I know (me included) is running away from it asap.
- batter 7y agoOur managers keep saying GCP is the best, and a lot of developers hate it. But who cares. And we also tried Firebase, luckily idea was abandoned.
- jsolson 7y ago> a lot of developers hate it Any particular complaints? (I work on Compute Engine)
- smt88 7y agoNot GP, but GCP's GUI is incredibly confusing and difficult to use. It is clearly a variety of products (poorly) stitched together. That has nothing to do with Compute Engine, and AWS is just as bad (if not worse). My new projects will all be on Azure because Microsoft has pivoted to a company with reliable investment in UI, developer-friendliness, and long-term support. Serving businesses has also been a core of their company from the beginning, whereas Google seems unwilling to provide the human support required and AWS is clearly at odds with Amazon's primary culture. It does seem like the underlying products in GCP are very good, but they mostly seem to replicate other offerings from Azure and AWS.
- etaioinshrdlu 7y agoThere are also those such as myself who instead feel that Azure's UI is by far by worst of the big three, and that GCP is not bad at all, and that AWS is big, complex, and ugly, yet practical. The long term support story of AWS is also great.
- smt88 7y ago> The long term support story of AWS is also great I agree in general, but specific services can be a problem. New server images have broken my apps, waiting for AWS to update support for languages or RDBMS can be painful, documentation is generally confusing (mostly because there are 10 ways to do every simple thing), and I bump into bugs regularly.
- adwww 7y agoAt my last work I was a developer occasionally doing things with their AWS account. I now run a large application mostly built in GCP and also now replicated in Azure for various compliance reasons. So although my experience with the 3 clouds is not equal, I've been exposed to them all, and actually massively prefer GCP for the UIs and CLI tools. AWS stll has better support by third party tools, and Azure is lagging behind everything.
- jsolson 7y agoThanks for the feedback here -- as I mentioned in another comment I'm generally fond of our UIs, and it's nice to know that I'm not _entirely_ crazy.
- jsolson 7y agoThanks for the feedback -- I'd be curious to understand what about the Azure UI you find most striking. For obvious reasons, I don't have much experience with it. I'm generally fond of our console, particularly the tools that show both the API and CLI invocations for most UI activities. On the other hand, I work on core virtualization, so the things I want to express tend to be very simple ("make me a giant VM", "make me a gianter VM", etc. :)
- tarjei 7y agoA big weakness is that all services have generic names so it is IMPOSSIBLE to google them and the documentation is weak and hard to navigate.
- jsolson 7y agoThanks for the comment -- I think (although I honestly don't know for certain) that the goal is for the names to convey something about what the service does. In particular, so that in the context of the catalog the general purposes of the various services are at least _somewhat_ obvious. The docs are always a work in progress -- anything you can recall trying to do with GCP that was particularly inscrutable (can't fix everything in one go, but one fix at a time is better than nothing :)
- matt2000 7y agoWhy are you running away from it? I have occasionally toyed with using it in a couple situations, just wondering what the dealbreakers are.
- exclusiv 7y agoNot positive if it's still an issue or not but they had a Geopoint type in Firestore but I incorrectly assumed you'd be able to do geo searches because of that. Their proposed solution was to pipe the Firestore docs to Algolia indexes and use their service. I did that and I love Algolia but don't assume anything because it's Google.
- JustAPerson 7y agoNot the person you responded to, but I just joined somewhere new and it's clear Firebase was the biggest mistake / is the biggest source of technical debt. It was helpful for bootstrapping 6 years ago, but now it stands out as the worst part of our tech stack. For our small shop, we will not be able to migrate any time soon. - Most frustrating are the outages we have no control over. It seems like every other day, the server running our firebase instance mysteriously disappears from the internet. We can ping `my-app.fibaseio.com` but receive no events from it. This lasts anywhere from 5 to 25 minutes. Usually there is no blip in the firebase status page. The main devs have given up trying to debug it. - We are nearing the resource limits of the paid plan for a single realtime database. We're working on splitting our one database into a master and sharding what we can. - The particular eventual consistency and transaction semantics require workarounds everywhere. If you want an atomic transaction, you have to perform it on some common parent, but you are also encouraged to keep your data model flat and normalize as much as possible. Our integration test suite is tiny and horrendously slow because we cannot rely on Firebase to be timely, so there are huge timeouts everywhere that regularly take ages. Every past attempt at tuning the timeouts to be shorter eventually causes spurious failures a week later. - Unless your data closely models the kind of chat application Firebase was built around, you end up needing a real database eventually. Not just to perform real queries with joins and complex logic, but also to essentially maintain indices that anemic mobile clients can use because the firebase filtered query semantics are limited to a single key. Now you need some kind of daemon to shuffle data in and out of your real database. Unfortunately, your real database is missing tons of foreign key constraints because that's the easiest way to handle firebase's eventual consistency. That's just my take a month after joining somewhere intimately coupled to firebase.
- Kiro 7y agoI have the opposite experience. Both my current employer and my old are migrating _to_ Firebase as we speak.
- corentin88 7y agoKind of the same. As a somewhat advanced user of Firebase (2 projects with >25K MAU each), it works extremely well.