11–20 of 516 posts
Isn't using AWS Lamba as your gateway, trapping you into using a specific service, just as much as firebase was?
> Always build your architecture in a way that will avoid becoming trapped into a specific service. Amazon’s AWS Lambda sitting between any services and your app is a strongly recommended path! Isn't using AWS Lamba as your gateway, trapping you into using a specific service, just as much as firebase was?
I find it hard to reconcile this suggestion at the bottom of the article > Always build your architecture in a way that will avoid becoming trapped into a specific service. Amazon’s AWS Lambda sitting between any services and your app is a strongly recommended path! - Build without depending on external services - You can do this by depending on this external service
> They have no phone number to contact, no way to dispute this other than email — which they have ignored us for over a month now without replying to our continued requests. Trapped. Doomed. We have no further options.
Sounds like Google did a great job with Firebase. Definitely gives you that Google-feel of unresponsive support and no hope when you have problems with any of their services. I bet they also have a "community" support forum or Google Group full of helpless people talking to a virtual wall. (Edit: Yep, they recommend Stack Overflow, Quora, and then their Google Group.. lol. Some things never change)
5 questions can be logged per year for one-on-one email support and then you're on your own. And this is for urgent requests.
I can understand not wanting to be inundated with wasteful questions but when Firebase is changing their API and pricing plans and you're trying to scale a product, and paying them lots of money in the process, support should be forthcoming.
They also don't respond on their Twitter handle, which is a further crime.
So in the end it was a coding problem, because you forgot to add Keep-Alive = true? If you use the provided SDK's it should be no problem then right?
> Always build your architecture in a way that will avoid becoming trapped into a specific service. Amazon’s AWS Lambda sitting between any services and your app is a strongly recommended path! Isn't using AWS Lamba as your gateway, trapping you into using a specific service, just as much as firebase was?
> Always build your architecture in a way that will avoid becoming trapped into a specific service. Amazon’s AWS Lambda sitting between any services and your app is a strongly recommended path! Isn't using AWS Lamba as your gateway, trapping you into using a specific service, just as much as firebase was?
I guess the point was that by adding the middleman between it there was more control --- We are self-funded and small group of people. We can't afford to hire a bunch of people to know about containers and servers and every little detail.
Thanks for your comments! Didn't expect so many views so quickly on this...