Traits of Serverless Architecture

Re:Traits of Serverless Architecture by vfc1 on Monday August 19, 2019 @12:56PM (#20739436)

I thought there would be competitors, I don't know why Firebase is not getting more adoption then, it's still a bit of a niche and Google does not seem to be pushing it as much as a couple of years ago, even though the product is better than ever.

[ Parent | on HN ]

Re:Traits of Serverless Architecture by sojournerc on Monday August 19, 2019 @02:51PM (#20740584)

In our case, it's because we have more than web/mobile clients talking to our API.

If the business case doesn't require partner/3rd party API access, then maybe Firebase is appropriate.

Mentioned elsewhere in the comments here is the risk of vendor lock-in.

Given Google's history of EOLing products from under developers, there is real risk in putting all the business logic eggs in the Google basket.

[ Parent | on HN ]

Re:Traits of Serverless Architecture by vfc1 on Tuesday August 20, 2019 @04:01AM (#20744728)

Firebase is like a web developer friendly version of Google Cloud, that it bases itself on.

It gives easy to use serverless CRUD (with Firestore), authentication, authorization, secure file upload, hosting and server-side functions for things like image processing or database triggers.

I don't think Firebase will be end of live anytime soon, worst case it's user base would get migrated to Google Cloud, as it's really just Google Cloud under the hood. I don't think it's an option for Google to give up on the cloud at this point, even though AFIK Amazon has the biggest market share.

[ Parent | on HN ]

Re:Traits of Serverless Architecture by latchkey on Tuesday August 20, 2019 @12:13AM (#20743775)

AWS Amplify is the competition.

[ Parent | on HN ]