Hi Jeff,
Any shared reasoning behind those advices? I assume it is because those approaches are increasing the total latency required for processing each incoming requests? I was experimenting on using Guice and its AOP method interception to replace my increasingly complex ContainerRequestFilter, and I love how much simpler things are after the I made the changes. It is disheartening to hear that those approaches turns out to be discouraged in App Engine apps by Google themselves. Is there any recording of the session, by the way? Would it be uploaded at some point on the (hopefully near) future? Cheers, Ibrahim On Thursday, May 16, 2013 1:52:51 AM UTC+2, Jeff Schnitzer wrote: > > I attended the "Autoscaling Java" session at Google I/O. In summary, the > advice is: > > * Don't use dependency injection. > * Don't use AOP. > * Hardcode configuration values as much as possible. > > In other words, go back to Java circa 2002. There was no discussion of > changing routing so that user requests don't see cold starts. I asked about > this in person - apparently they're still "talking about it" and nothing > has been done about it. > > I am sad. > > Jeff > -- 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 http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
