[google-appengine] Modules vs Multiple Scripts?

2014-05-05 Thread ZTNXiLUzVm
I am developing in App Engine with Python and I understand what Modules are 
from reading the 
documentation,
 
but I thought the process of splitting your code into multiple scripts and 
mapping them in the app.yaml file was supposed to accomplish the same 
thing. Does splitting the code into multiple scripts not actually do 
anything except make the code more organized?

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.


Re: [google-appengine] Modules vs Multiple Scripts?

2014-05-05 Thread Vinny P
On Tue, Apr 29, 2014 at 5:18 PM, ZTNXiLUzVm  wrote:

> I am developing in App Engine with Python and I understand what Modules
> are from reading the 
> documentation,
> but I thought the process of splitting your code into multiple scripts and
> mapping them in the app.yaml file was supposed to accomplish the same
> thing. Does splitting the code into multiple scripts not actually do
> anything except make the code more organized?
>


You may be getting a little confused from the terminology. A Python module
( https://docs.python.org/2/tutorial/modules.html ) is a file containing
Python code. As you said, splitting up your app into different files helps
with organization, code reuse, and so forth.

An App Engine module is completely different and not related to the concept
of Python modules except in the most generic way. It's true that GAE
modules help with code organization, but it's much more than that. Each
module tends to be a fully featured application or self-contained service:
for example, one module is a web site, another module implements the API,
yet another supplies the backend heavy-lifting logic, and so forth. GAE
modules also supply other benefits: logs are separated and you can specify
different instance sizes.


-
-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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.


Re: [google-appengine] Modules vs Multiple Scripts?

2014-05-05 Thread Diego Duclos
Also important: each module is allowed to scale up / down seperatly, which
means you can configure the more important things to scale faster while
allowing slower scaling (and thus lower costs) on less important modules


On Tue, May 6, 2014 at 5:37 AM, Vinny P  wrote:

>
> On Tue, Apr 29, 2014 at 5:18 PM, ZTNXiLUzVm  wrote:
>
> I am developing in App Engine with Python and I understand what Modules
>> are from reading the 
>> documentation,
>> but I thought the process of splitting your code into multiple scripts and
>> mapping them in the app.yaml file was supposed to accomplish the same
>> thing. Does splitting the code into multiple scripts not actually do
>> anything except make the code more organized?
>>
>
>
> You may be getting a little confused from the terminology. A Python module
> ( https://docs.python.org/2/tutorial/modules.html ) is a file containing
> Python code. As you said, splitting up your app into different files helps
> with organization, code reuse, and so forth.
>
> An App Engine module is completely different and not related to the
> concept of Python modules except in the most generic way. It's true that
> GAE modules help with code organization, but it's much more than that. Each
> module tends to be a fully featured application or self-contained service:
> for example, one module is a web site, another module implements the API,
> yet another supplies the backend heavy-lifting logic, and so forth. GAE
> modules also supply other benefits: logs are separated and you can specify
> different instance sizes.
>
>
> -
> -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 google-appengine+unsubscr...@googlegroups.com.
> To post to this group, send email to google-appengine@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-appengine.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-appengine@googlegroups.com.
Visit this group at http://groups.google.com/group/google-appengine.
For more options, visit https://groups.google.com/d/optout.