Ok, I get it, welcome to the world of elastic apps. But still there are few simple things google could do to ease the pain... If you are a small startup, with small traffic (just a few F1's) and a couple devs, you have money for few month to run, what you want to do is probably keep making features like hell (and consuming memory)... Don't really care for long startups (simply because not doing anything important and my client side handles timeouts gracefully) as long as google won't start killing my instances. I'm worried because I read a lot here about "bad days" when startup times are 3-4 times compared to normal and in that case this could happen... There are tons of projects like us and some of us can go big, so why not make small effort and make the life a little easier for "conventional" java apps. For example, would it be totally impossible to soften the 60s limit for the loading requests and make it double? Some of the comments above (by Jeff and others) regarding pending queue do not look too hard to implement either. It will make many project owners happiers (even if they won't go as big, but maybe they don't need to), so google wins also.
On 22 июл, 12:18, "Drake" <[email protected]> wrote: > I don't use frameworks in Python either. Ask my Dev team. They all but riot > when they find a library they want to use and I say, figure out what it does > and make your own, we don't have room for that thing. > > Java aint Ruby on Rails. (or Oh please don't let it be) I get that the appeal > of Java is that it is older than dirt and there is a framework for everything. > You can use 1 frame work if it is a small one :-). > > You are trading rapid elasticity for ease of development. You have to remember > that when you are small Servers are cheap and humans are expensive. When you > get to Google Scale that reverses. GAE is optimized for near Google scale. > (not all of Google, but Small Google product) if you are 1/1000th that the dev > resources for optimization will kick your ass. Just like the guys who say they > wont' do it. Those are guys who don't spend $50k a month on hosting. When the > amount you spend is double the cost of a dev, it is time to look at ways to > cut that hosting in half using a dev, because you will break even, and give > higher QoS. > > > > > > > > > -----Original Message----- > > From: [email protected] [mailto:google- > > [email protected]] On Behalf Of Aleksei Rovenski > > Sent: Sunday, July 22, 2012 2:05 AM > > To: Google App Engine > > Subject: [google-appengine] Re: Startup time exceeded...on F4?! > > > I can understand that GAE is more optimized for python than for java. > > Maybe it is a highly specialized tool for really tiny apps that use no > > frameworks. But I don't get one thing. How Google plans to compete for java > > apps by selling platform that forces you to not use frameworks? I simply > > refuse to go back into the 90's (in software development aspect, no problem > > otherwise :)). I simply do not want to drop dependency injection and other > > patterns I have been doing for many years already. If I must, then I think > > it > > just isn't worth it. > > Seriously Java is about frameworks. Saying not to use frameworks in java is > > same as use python instead. No thanks. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
