Is this suitable today with an app built with Python 2.7 + Standard Environment

[haopei]

I am hoping to set up endpoints for my project. Do you have any advice on what route to take? Is the endpoints-proto-datastore still applicable?

[tmst]

I know this is late, but thought I'd share my 2 cents' worth. I have a basic app consisting of 4 models and all the relevant methods running on App Engine using EPD. It's just been chugging along for a couple of years, now. It authenticates against Gmail addresses using OAuth2. My only real gripe has been its unintended (I believe) limitation in patching nested StructuredProperty instances wherein omitted request parameters result in fields getting stomped on with null or default values.

[haopei]

Thank you for sharing @tmst. I wonder if App Engine is suitable for such a set up today. I know the Google team is focusing on Firebase.

[tmst]

I looked around for information on this. I got the idea the App Engine is still a fully viable solution for new apps that won't need to support the mobile APIs. I'll probably start looking into Firestore in any case just to be on the safe side.

[haopei]

@tmst, if this is true, then it sounds to me like GAE will become out-of-favor for developers who are choosing a platform because people would choose to go with a platform which allows Mobile API more easily.

There is also something to say about platforms which already exist on GAE that wishes to extend to mobile; developers may feel contained here. This is why I am second-guessing whether the google team will pay any more attention to the GAE service in general.

[dgaedcke]

It is a mistake to consider Firebase a full replacement for GAE. Firebase is an excellent product but (except in very light circumstances) you should NEVER consider Firebase to be your PRIMARY DB. It makes more sense to store data where integrity can be enforced and just use FB for the web-sockets implementation.
My comments take no position on whether this library is still valid or not ... I'm under the impression (and commit history shows) that it's not being supported today.

[haopei]

It makes more sense to store data where integrity can be enforced and just use FB for the web-sockets implementation.

Thank you for sharing @dgaedcke. On this note, can you share an example of how Firebase works alongside another integrity db? I am under the impression that Firebase's Firestore can be used to power apps fully, including the role of the primary DB.

[dgaedcke]

I've not looked at the new Firestore so perhaps it looks a lot more like a real DB than the original Firebase DB did. But if that's not the case, you will create all kinds of problems for yourself with schema-enforcement and versioning if you don't have a versioned API between your client code and the table defs. I prefer to use GAE datastore as primary db and just sync real-time data from GAE to Firebase for reading by the client. In general, I don't let my clients do much writing to a schemaless DB without anything to manage versioning or force consistency

[dgaedcke]

Here is where I saw that this lib does not work well with Endpoints V2