2009/1/29 E. Naraki <[email protected]>:
>
> Hali,
>
> yes it is possible to for AppEngine to handle 100,000 users with many
> concurrent requests.
> Of course your app will not be allowed to use such resources until
> they release the payment system to break out of the initial free
> resources.
>
> AppEngine is built with Scalability in mind (http://en.wikipedia.org/
> wiki/Scalability)
> and will allow you to reach an inifinite capacity, given you provide
> an inifinite amount of funds (at competitive market price).

Not even Google have infinite server capacity - sure they have a lot,
but inifinite ?

>
> As for advice on how to begin with AppEngine and tap into the massive
> potential it has.
> Please check out http://php.net

why php.net? Do you know something we dont?

http://code.google.com/appengine/docs/python/runtime.html

This is not bad:
http://code.google.com/appengine/docs/python/gettingstarted/

>
> Let me know how it goes,
> E
>
>
>
> On Jan 28, 9:48 pm, "h.ali" <[email protected]> wrote:
>> Hi guys,
>>     I'm newbie to the google app engine, and i was wondering whether
>> you guys could help me out in a problem. I want to develop an
>> application which would need to cater for like 100,000 users using it
>> simultaneously. All the users would be sending requests to the serve a
>> couple of times a minute and this would put i think a huge load on the
>> server.
>>
>>     Would the Google App Engine be able to handle this? Also, if
>> anyone can give any advise on how should i proceed, that would be
>> greatly appreciated.
>>
>> Thanks,
>> HAli
>
> >
>



-- 
Barry

- www.nearby.org.uk - www.geograph.org.uk -

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to