AppEngine with Endpoints

Andrew James

unread,

Jun 9, 2016, 10:15:43 AM6/9/16

to Google App Engine

From the tutorials I have seen, you can package html/css within an Endpoints app, effectively creating a dynamic web app. Is this good practise, or is the recommended approach to create a separate app (containing the front-end code) and host it in app engine?

Juan Antonio Fernández Sánchez

unread,

Jun 10, 2016, 7:20:03 AM6/10/16

to Google App Engine

Hi, Andrew:
I'm developing a project in that I have two apps, front-end and back-end. In the front-end i have a app writed in AngularJS and in the back-end I have other app composed by few microservices, and one of these is a cloudendpoint, to communicate with the front-end. I don't know if this is the best way to do this, but this it's fine for me.

Nicholas (Google Cloud Support)

unread,

Jun 10, 2016, 1:50:10 PM6/10/16

to Google App Engine

Endpoints are an excellent choice for backend APIs. A very common paradigm is to have a front end (browser or mobile) deliver the UI and communicate to a back end API done with endpoints. This separates data manipulation from data presentation and is definitely a good practice. The Getting Started tutorial is a great example of this in practice.

Kaan Soral

unread,

Jun 11, 2016, 8:35:23 AM6/11/16

to Google App Engine

I think your answer is No, it's not a good idea to create a separate app

One app can do it all, front-end is served by the back-end too

If I understand your question correctly that is

Reply all

Reply to author

Forward