I had to mention it because apart from the really interesting Channel API there is a new “Always on feature” which, even though it costs money is a possible solution to the loading issues with using Grails on Google AppEngine.

There is also a possibility of activating Warm-up requests to try to predict in advance when there is a need for more instances. Which should help out even more with running Grails on AppEngine once you reach the limit of the preloaded three instances of the “Always on”-feature.

Also there are some severe changes to the limits for running background tasks and Cron jobs, which should allows more computation intense applications on AppEngine.