GAE / J: Development and production environment

Question

What are the main differences between GAE / J between development and production environments.

• What should be double-checked in production?
• What kind of storage differences should I expect?

Answer 1

• Single-threaded development environment
• No request timeout
• No bang index , infact dev env doesn't use indexes at all for queries
• No async URLFetch
• No async datastore
• Obviously no statistics query / search interface
• No waiting time to build the index
• Lack of data warehouse timeouts
• Without reducing capabilities

Answer 2

dev () . .

dev , , , sqlite.

javamail .

API- oauth .

Cron .

, , .

JDO, dev() (persistall()). .

, , .

Answer 3

, ; , - "" ( , ), /awesomeness .

, :

• (30 , 10 , 10 Urlfetch)
• -
• ()

, , API (--), ; .

Viceversa, a development server that even allows Sqlite, has serious limitations when trying to save / update thousands of objects; The production server is a powerful beast.

Answer 4

In addition to the above, I found another difference. In the Dev environment, you can store non-serializable classes and objects in session attributes. But be careful to keep only serializable classes during production in session attributes, otherwise you will get an exception.