I've been interested in Modules, mainly to: 1) Seperate the logs / components of the app, to ease the debugging and monitoring 2) Hope to increase the performance, leave the frontend instances to user-facing requests only (?)
The documentation is very adequate, however, as all services, you have to dive into it to actually learn it What I learned: 1) You have to use a manual appcfg command, manually cd the directory, appcfg update app.yaml module.yaml's (Which is something everyone should do anyway, imo, I only use the gui/launcher for deployment, I will probably not do that anymore) 2) Each module seems to be like a separate app, that shares the appengine services like datastore etc. (Great!) 3) Each module gets uploaded separately (the command does this), multiplying the deployment time/risk (It's kind of obvious, as module's are separate components, however the risks are unknown) (Does the rollback command work the same way? - for example this is one risk, unknown) 4) The UI/AppEngine Console improves with module tabs at each tab like Dashboard/Instances/Logs/Versions (Great!) 5) Each module .yaml should include everything, similar to app.yaml, like libraries etc 6) I'm guessing the costs will increase a bit, however, it might also decrease the costs of some high traffic apps as it will allow throttling at the backend level I have some questions to those who are experienced with Modules: 1) Are there any side-effects, not obvious thing that are major road blocks? ( Are the GCS/Datastore/Memcached all shared etc? - They should be ) 2) How does the SDK handle things? (I've yet to test the SDK) 3) Any advice? -- 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 http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/d/optout.
