On Wed, Nov 6, 2013 at 1:55 AM, stephanos <[email protected]> wrote:
> Generally, I was wondering about the feasibility of urlfetch for internal > calls because I read somewhere that you can only have so many parallel > calls. > > Yes, that's correct. Urlfetch quota limitations and per-minute limitations are still in effect even while calling intra-application services. This has been commented on before; see this issue: https://code.google.com/p/googleappengine/issues/detail?id=8052 In general if your application is small it won't run into these types of problems. The per-minute quotas are pretty generous and most applications don't need to concern themselves with this. However if you're planning on writing a large application or an application that scales up and down quickly, you will probably hit these limits. If you do have a large application, consider purchasing a Google cloud support package: Google support can do some tweaking on their end and help recommend specific optimizations. On Wed, Nov 6, 2013 at 1:55 AM, stephanos <[email protected]> wrote: > > The question, as you suggest, is whether I put these shared capabilities > into shared libraries or a shared modules ("services"). By isolating > capabilities into services I would always only have to update and deploy > that one service but the required communication overhead worries me. > Frankly this is more of a personal preference choice - do whatever you feel comfortable with. The only thing I would suggest is that you build a mockup for the shared modules use case and stress test it - you'll get a general idea of the performance profile. ----------------- -Vinny P Technology & Media Advisor Chicago, IL App Engine Code Samples: http://www.learntogoogleit.com -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine. For more options, visit https://groups.google.com/groups/opt_out.
