6 ms·
I like Firebase, but will never use it unless I absolutely have to. It's not anything they've done, it's what happened to Parse. I built a half dozen apps using
by valuearb 10y ago
I like Firebase, but will never use it unless I absolutely have to. It's not anything they've done, it's what happened to Parse. I built a half dozen apps using Parse as the cloud backend because it was so easy.
My last project my CTO chose Parse to build a backend for a Website. Parse Cloud Code was fairly limited, we'd have to do a separate server for Stripe for example, but again it made the specific client project really easy to do (and he had been tasked on building it really cheap given our crazy CEO had given the client a fixed bid). I knew it was screwy but said "At least we can be confident that Parse isn't going away any time soon" since Facebook had bought them.
I finished the site on time, on budget, the web service demoed great at it's launch show, and the client signed up a ton of customers and was just waiting for our e-commerce implementation to launch their important new business.
Then Parse was canceled.
- matz1 10y agoComplaining about change in tech world?
- valuearb 10y agoChange is fine. But it also impresses upon me the value of open source technologies.
- rrdharan 10y agoBut Parse was opensourced, before it was turned off.. And opensourcing doesn't help with offloading operational complexity anyway. So I fail to see how these are connected.
- dragonwriter 10y ago> But Parse was opensourced, before it was turned off.. And opensourcing doesn't help with offloading operational complexity anyway. In theory, it means you can pay someone other than the original owner to handle the operational complexity for you (so long as the whole stack, including any necessary backend pieces, is open-sourced); it doesn't guarantee availability, especially at a price you are willing to pay, but it does mean that it's legally possible.
- amenod 10y agoOk, but Parse was opensourced, so you could basically just run your app on that, or am I missing something? If you wanted to use cloud offering, I'm sure you could pay someone to take care of it for you. Are you worried about future development? Other than that, there really are no guarantees. Project leads move on, companies close and get acquired, projects get replaced... I had to develop for 3 different google cloud messaging platforms for the same app, and I don't even consider myself Android developer. Such is life.
- azinman2 10y agoWhat parse open sourced is not what they were running on their backend. It also now doesn't come with devops, new features, etc.
- amenod 10y agoWasn't it? I didn't use them, but their shutdown notice [0] reads like they opensourced whatever is needed to keep client apps running. I agree it sucks though. The code gives you more time, but since it's not maintained and actively developed anymore you still need to migrate to another platform eventually. [0] http://blog.parse.com/announcements/moving-on/ http://blog.parse.com/announcements/moving-on/
- azinman2 10y agoThey gave you something equivalent to a single server solution. So for simple apps it's fine, but if you have a complicated app that needs a lot of distributed networking to handle the load then good luck. Don't forget you also need to migrate all your code, host your own servers, handle downtime, etc.
- intrasight 10y agoI also used Parse on a project. They pulled the plug on Parse half-way through our development. I recommended to client that we switch to Firebase. Client asked "couldn't Firebase go away some time?" I answered that I was sure that Firebase would go away some time. But in the mean time, we are using Firebase and are very happy. I think that a bigger risk than Firebase going away is Firebase deciding to fire you as a customer.
- ereyes01 10y ago> I think that a bigger risk than Firebase going away is Firebase deciding to fire you as a customer. This is what it felt like at one point a little over a year ago. I host a SaaS on Firebase with some paying customers. They started having infrastructure problems and I was down for a whole week. Despite me sending them specific curl commands that reproduce the issue (30-second latencies followed by 500 replies), they really didn't have the same sense of urgency that I had. At first, they didn't even seem to believe me that there was a real problem happening. After several days they finally fessed up to the problem, and then like a day or two later, my app started working again. The incident left a really bad taste in customers' mouths, and who can blame them... I was lucky not to lose them all! So for a week, Firebase effectively fired me as a customer. My impression is that the outage didn't affect a large portion of their users. When that's the case, you end up needing Firebase a whole lot more than Firebase needs you.
- amygdyl 10y agoFor me, the Parse story, albeit I never knew it in depth, or intimately or even directly as a user, is the best summary I can find, is where OSS fails: the huge blind spot of freedom when it comes to hosted solutions, where the OSS licenses fail to apply. In extremis, this has created the precise opposite of a rich commons, for giants such as Google would not likely exist, if they were required to release their code if providing a service was considered strictly to be "publishing" the OSS licensed software in a modified form. It has allowed, for instance, a strong supporting argument to use Azure, where we have desired cloud delivery, certainly over a number of smaller cloud service providers that could have contended. In any event, wherever we have found need for supporting tools or deployment tools, or any instrumenting facility, our decisions have gone against any small independent or startup supplier who value add atop OSS, at least in any critical code paths. I should add, in my Dictator For A Day fantasy, I would also write into copyright law, a requirement that all defunct companies incapable of discharging in full their tax obligations, become required to deposit their source repositories as public domain articles. I don't know what the US equivalent is, but in the UK, defunct company works become copyright the Treasury Solicitor, i.e. Crown property, which the Treasury Solicitor may then express no interest in, subsequently letting the copyright ostensibly (bar pre-existing, prior, claim) to pass into public domain. So, in a obscure and narrow sense, my wish does actually exist, in one jurisdiction, for some rare cases, including one I pursued. I fear, as intrasight notes, very much indeed fear that there are dangerous factors in the way dependencies are introduced, how users, nay whole startups are enticed (if not lured) into relying upon "ZeroSLA" circumstances, which are the antithesis of the objectives espoused by the open source founding progenitors and movement generally. The ominous prospect of being "fired" as a client and customer, ultimately at the pure fiat of "benevolent giants" possessed of fathomless resources from which mere mortals pray for beneficence, seems to be not a science fiction future, but the dystopia of the present. As recent stories, including that about GitLab, but also comment abroad about FB's code practice, and a apparent generational disconnect from past established (and even vilified) "enterprise values" increasingly reveal, it is insufficient to simply blame even severe mistakes, on young highly intelligent management, for there appears to have swept across the programming world, a cultural lack in oversight, that is becoming a measurable, real, present, risk. It isn't a subject I like to contemplate much, because it is so hard to suggest positive, immediately actionable, clear insight or values that apply, except by applying such in immediate practice, wherever one can, and even so "enterprise culture" is also values, and in a cultural mismatch, such things are incredibly hard to argue effectively, when a complicated balance has to be struck. Certainly, this is far harder, than it was twenty years ago, when one felt it possible to align with one or another of the fresh, youthful, enervating movements that have since swept consciousness and created so much economic activity, even amid general recession. Only, the net effect, and net economy, is a vision far far removed from one I think anybody ever hoped to see. Who, for instance, following the anti trust trial against Microsoft (which riveted me, and I ended up reading the bulk of transcripts and depositions, which I am not sure one can even find online any more, but were a education themselves) ever imagined four - letter oligopoly was the next, potentially final, stage? Certainly, it is no longer as simple as "pick a license" .... ninja edit: typos, minor clarity
- mbleigh 10y agoFirebase engineer here. We recognize the anxiety that comes with a hosted solution. That being said, Firebase has seen enormous and growing investment from Google (see e.g. Fabric acquisition). Firebase feeds directly into two huge businesses that Google cares deeply about: Cloud and Ads. I can't predict the distant future, but unless Google's core business shifts drastically Firebase isn't going anywhere.
- enraged_camel 10y ago>>Firebase isn't going anywhere. If experience has taught us anything, it's that it's pretty naive to say this about anything owned by Google. I mean, things like Google Wave and Google Buzz were huge initiatives at one point too.
- mbleigh 10y agoIs it possible things will change? Of course. I was just trying to illustrate that, unlike Parse and Facebook, Firebase has a clear relationship with core Google businesses. We will never be able to fully dispell these worries, but I think there's pretty strong evidence in support of Firebase's prospects. Our developers will have to judge if the value we deliver is higher than the small-but-non-zero chance of it going away. I certainly think it is, but I'm pretty biased. :)
- kaishiro 10y agoSo, I see this argument over and over again with re: to Google, but what I've never seen is Google closing shop on anything in their GCE offering. This certainly doesn't mean it's not possible, but I'm not sure comparing the discontinuation of one-off products to any of the GCE offerings is fair. It's absolutely possible I'm being naive here - just one person's take on the situation.
- CobrastanJorji 10y agoMost of the canceled Google products have been free, consumer-facing, chat apps. Have they canceled any cloud products? App Engine's been around for like a decade now.
- bsg75 10y ago"There is no cloud, only someone else's computers." Building on an external platform is fine for expediency, as long as you have a backup plan.
- marknadal 10y agoGiven that Firebase hasn't shut down yet, and they just announced Firebase Cloud Functions and stuff, I think that is a pretty strong sign of healthy growth. Firebase (and Rethink) are some of the bests out there, and like Slava said about license concerns, why worry about what might happen... when using these systems let you avoid worrying about a bunch of painful things NOW? I'm still the type though that prefers to use Open Source tools and not have vendor lock in, though. That is why we're building https://github.com/amark/gun https://github.com/amark/gun which I often describe as an Open Source Firebase. The goal is that it is self-healing (P2P architecture) so you don't have to worry about DevOps either. Recently we ran load tests on low end hardware doing 2K table inserts a second across a federated system - and we hope to get this up to 10K table inserts a second on a free Heroku instance (if this is physically possible). That said, use tools that make your life easier NOW, be that Firebase or not - the future is always going to have its own challenges.
- aub3bhat 10y agoI completely agree. Parse at least was not too different from a vanilla Mongo setup. Firebase on the otherhand looks brutal to move/switch away from.
- sorenbs 10y agoThis is a sentiment we struggle with a lot at https://www.graph.cool https://www.graph.cool Being based on GraphQL (an open standard) and AWS lambda (a service that most certainly isn't going away) helps, but it is tough. What would it take for a hosted backend to make you comfortable using it?
- arikrak 10y agoOne thing you can do is look at how much the company has invested in the product. There may be a reasonable risk they may shut it down if it doesn't tie into other products that the company offers and they don't try to integrate it with other products (Parse). On the other hand Google has invested heavily in Firebase and it offers far more features than when they bought it, and it integrates with many other Google products. (Disclosure: I work at Google, though I'm not connected with Firebase.)