Hi, George, thanks for the response. I have forked a new branch with specific intention of changing my main modules into microservices. I'll get those modules as services slightly restructured and communicating first then I should have my api core in place and just need to add routing. I'll probably just roll my own api authentication, write up some docs and see how she files.
I'll be sure to pop another question over if I run into any road blocks. Cheers On Mon, Aug 7, 2017 at 9:11 PM, 'George (Cloud Platform Support)' via Google App Engine <email@example.com> wrote: > Hello Richard, > > If you existing application is fairly modular, all you need to work on, to > convert it to a micro-services-based app, is to at least convert your > imports and read-writes from various models to calls via HTTP. The new > services would provide full isolation of code; the only way to execute code > in these services is through an HTTP invocation, such as a user request or > a RESTful API call. With more work you may be able to re-think the existing > modular structure to reduce dependencies and optimize calls, in the end. > > You can gather more detail on the micro-services architecture and specific > communication paths from the “Building Microservices: Inter-Process > Communication in a Microservices Architecture > <https://www.nginx.com/blog/building-microservices-inter-process-communication/>” > documentation page. > > 1) The best approach to building and endpoints-based application using > services depends on your needs and the architecture that arises naturally > from the analysis of those needs. More information from the “About Cloud > Endpoints Frameworks” page > <https://cloud.google.com/endpoints/docs/frameworks/python/about-cloud-endpoints-frameworks> > and the “Converting Backends to Services” document > <https://cloud.google.com/appengine/docs/standard/python/modules/converting> > . > > 2) Some of the characteristics of inter-services communications in the > micro-services architecture are: > - Code in one service can't directly call code in another service. > - Code can be deployed to services independently. > - Different services can be written in different languages, such as > Python, Java, Go, and PHP. > - Auto-scaling, load balancing, and machine instance types are all managed > independently for services. > > 3) The optimum structure of your architecture should reflect your > application needs. Usually, starting from existing modules might prove > easier than rewriting the entire application specifically for the > micro-services architecture. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Google App Engine" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/google-appengine/JCy33JUtW8U/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > google-appengine+unsubscr...@googlegroups.com. > To post to this group, send email to firstname.lastname@example.org. > 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/d9940f79-8362-4cdc-9287- > 2c064b88b058%40googlegroups.com > <https://groups.google.com/d/msgid/google-appengine/d9940f79-8362-4cdc-9287-2c064b88b058%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to email@example.com. 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/CAOrJiXAoebET1haX_FN%2BUZYb6%3Dxr8iupyLBhpx6vAYt8Ug0Cyg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.