I'm sure not all of us have the cash to pay for the amount of servers the app engine requires. Also, they pretty much use jetty for the frontend, they use an rpc system to communicate with whatever their backend is coded in. (at least from briefly scanning the the gae docs)
2010/8/13 François Masurel <fm2...@mably.com>: > What about the Google App Engine for Java platform ? > > It's powered by Jetty though, not Tomcat. > > François > > On 13 août, 11:28, Miguel Morales <therevolti...@gmail.com> wrote: >> > Do you know that most of the web sites, services and whatever on the >> > internet are powered by Java and by a good percentage by Tomcat? Java >> > = slow is bullishit at least since five years, so please don't spread >> > FUD any longer. >> >> Yes, I know. I used to be a sysadmin for a few datacenters. I know >> how tomcat applications behave. >> Like I said, in server environments the jvm is really good. I use it >> myself. It's fast enough, but by itself, doesn't scale very well. >> What popular website runs on pure java code? >> The VM as-is doesn't do well in slower/older hardware. The amount of >> ram required for each instance is ridiculous. >> Run a decent amount instances of your app and your server is toast. >> Or if your app scales in one vm instance, it's still not worth it. >> You're stuck with the usual perils of multi-threaded programming, >> without any gains in efficiency or grace of scalability. >> Locked hashmaps are cool, so are queues, but for anything real world >> you'd most likely connect to a network database. At that point you >> might as well code your app in a scripting language and increase your >> productivity maintaining a relative performance. >> >> Then, what about scaling your app server wise? You're again network >> bound over communicating between the instances. >> Might as well skip all those optimizations and use something more >> expressive and code faster. >> >> > This is meaningless given some context. There are plenty of benchmarks >> > around that demonstrates than Java or C are faster. The JIT >> > technology, BTW, allows for higher optimization than C, since it can >> > only optimize statically. Of course, single benchmarks aren't >> > meaningful, since in a real world project one have to do some >> > trade-offs. There are many real-world examples that can be done, just >> > the first one that is public and comes to my mind has been recently >> > presented at Jazoon. See >> >http://jazoon.com/Conference/Thursday/OMullane, slide #40, which I'm >> > copying: >> >> I don't know of any popular fast java applications, despite all these >> features. >> Again, Java is ok, great for what it does. But > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- http://developingthedream.blogspot.com/, http://diastrofunk.com, http://www.youtube.com/user/revoltingx, ~Isaiah 55:8-9 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
