I don't think Firebase is like GAE. GAE managed a backend server in a scalable way; you're still programming a backend application. Firebase on the other end is suppose to get ride of the backend application.
I think Google Cloud Endpoint was trying to solve the same use case than firebase. The various Server-less platforms (AWS lambda, cloud function) are similar to the original GAE model (before they introduced instances) with a shift away from the REST api. On GAE you map a http handler to an event (http request, pub/sub event, email received, etc...); on Server-less apps you map a function to an event directly. It's a more boilerplate if you're just writing REST API, but I guessing it's more efficient and more elegant for other type of events than HTTP request. On Sunday, 2 April 2017 19:09:01 UTC+1, pdknsk wrote: > > You mentioned Firebase. I don't use it, but isn't it fair to say that > Firebase is what App Engine originally meant to be? Might be a piece of the > puzzle. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a8a91594-8af0-406f-82ce-5e9d982c4074%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
