4 ms·
"All too often a single HTTP request will have 4 or 5 database queries in it, and that is regarded as normal." Is this really normal for a Java app? A typical
by nikz 16y ago
"All too often a single HTTP request will have 4 or 5 database queries in it, and that is regarded as normal."
Is this really normal for a Java app? A typical Rails app (either built by myself or someone else) would have tens of queries in a request and still complete in under 1s. That was my experience with PHP too.
- nl 16y agoWell yeah, Java apps have tens of queries too, and they complete in under 1 second. But that won't work on AppEngine.
- jasonkester 16y agoThat was the final nail in appengine's coffin for me. You get one query per page, preferably a get by id, and you'd better not want to do anything fancy with the result either. Need more? It's simple. You just port away from appengine. Or you jump through the insane hoops the author describes just to get your mildly complex pages composed and out the door.
- sematronic 16y agoThe choice of a platform has nothing to do with the response times. The author was referring to a typical "enterprise" app, which might call several backends at once. Java or no Java, some of them will not be that responsive, and it will increase the overall response time. His point was that the "enterprise" way of thinking of what is "normal" should be reconsidered when you switch to GAE -- Java has nothing to do with it.