> I will be generous and assume for the moment that this makes sense for > your particular application. At best you are arguing that you have a wacky > application. You won't find too many people building business apps that way, > especially when you have elaborate transactional logic. > There are sometimes good reasons to compose an app out of more > fundamental services, but this should be driven by application design > - not a dumb limitation of how many classes you can pack into a JAR before > instance startup times get out of control. > > > Web.XML at the individual app, but path routing is handled by the > > If I went the web.xml route, it would map 326 servlets. Not really fun. > There's a reason people started inventing "web frameworks" in the late > 90s... because that kind of programming sucks when your app is even mildly > complicated. >
And this is where you prove your stupidity. This is how every large "app" on the planet works. A load balancer serves requests to the right "app" and each app is optimized for what it is supposed to do. Data is shared between apps using API's, Memcache, and Datastore. I know what an "end point" is. Apparently you don't. Each of what you call and End point should be a micro app. A single purpose App that handles one type of request. This lets you build my Unicorns. Fast little apps that do one thing, and do it fast. Also because they do only one thing they get to maximize their instance memory. Java gets REALLY slow and has more warm ups when you have 200 megs of code and 128 megs of ram. (as in it doesn't work, and if by some miracle it does make it past warm up typically you hit soft memory limit and it dies) You clearly are building Monolithic code in a world of Micro-instances. STOP IT. You will only have pain doing so. Build single purpose instances that do what they need to do. I'm sorry your app is too small for there to always be one instance doing each task. That's not my fault. Get more popular or something. In the mean time use lazy loads so that you can fake having instances that do one and only one thing by only loading enough stuff to do one thing until you need to do that other thing. I'm clearly not going to convince you to do anything, because you don't want to. You want somebody else to fix your problem so you won't even look at solutions. At which point I have to point out you are always going to be sad and miserable. PS Survivor Finale. And Comments aren't static. Nor are "post to facebook". Nor are Oauth calls. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
