Ok, I'dd like to clear this up: Without having a copy of the ndb.Model in your microservice you cannot access it from the ndb client library.
The point of the symlinks is to provide that access without having to copy the model definition in everytime you make a change to it. Ok, you can cut and paste, but it's easier to symlink it. Of course when it is uploaded it is a static copy of the model definition, not a link... Perhaps my question should have been more specific up front... However, I think there is a clear use case for sharing models amongst micro services in the same application, without having to share the model amongst all those services that use it. This is problematic as far as maintainence is concerned. Does that clear my thinking up? On Thursday, October 18, 2018 at 12:53:21 AM UTC+3, Julie (cloud platform support) wrote: > > This seems like a design/code issue which would be best posted on > Stackoverflow. It would also be helpful to clarify why redefining your user > class in GAE code when you are using NDB to get / put the data would not be > sufficient. > -- 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 google-appengine@googlegroups.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/9ead276b-8f1c-4747-8972-5592a2cc7952%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
