Dedicated Memcache
Dedicated memcache is now in Preview. App Engine developers already enjoy a free shared memcache that allows them to cache data in order to improve performance, but in some cases your application needs more control over your cache. With dedicated memcache you can purchase in-memory data caching capacity exclusively for your application, cache more data and drive up cache hit rates. With higher cache hit rates, dedicated memcache can also reduce Datastore costs and make your application faster than ever.
App Engine now has two classes of memcache service: shared and dedicated. No code changes are required when moving to dedicated memcache from shared. Starting today, billing enabled applications can select dedicated memcache on the App Engine admin console’s application settings page. Dedicated memcache is priced at 12 cents per GB per hour.
Git Support
Many developers have told us they work with standard development tools such as git and they don’t want to have to context switch to deploy to App Engine. Today we are making it even easier to deploy Python and PHP applications to App Engine with the Source Push-to-Deploy feature.
$ git push appengine master
Below is what a user would see after enabling this feature for an example project ID ‘polar-automata-277’:
With this release of App Engine we are making Push-to-Deploy Preview available for anyone to try.
Modules
App Engine Modules is a new feature that allows developers to split out large-scale applications into logical components that are able to share stateful services and communicate in a secure fashion. Not all components within an application are equal and often times they require their own performance configurations, authorization, and versioning. With Modules, developers can start splitting their apps with a single configuration change:
mobile-frontend.yaml
----------------------
application: insta-lbs
module: mobile-frontend
version: 1
runtime: python27
You can create modules for any support languages in App Engine. For Java, the packaging system for modules is the Enterprise Archive (EAR) mechanism. See an example of a Maven Ear project with App Engine modules at https://github.com/GoogleCloudPlatform/appengine-modules-sample-java. For more information on this feature, be sure to check out our docs (Java | Python).
PHP Runtime
With over 1000+ developers building PHP apps, we’ve been thrilled with the early interest. Based on your feedback - in the 1.8.1 release of PHP we announced support for the much-requested mcrypt, iconv and mbstring extensions, as well as the ability to include and/or require PHP scripts directly from Google Cloud Storage - helpful when using templating systems such as Smarty.
In this release we’ve added a number of improvements to our Cloud Storage integration. We’ve also launched a drop-in plugin for WordPress that adds support for using Cloud Storage for storing uploaded content, and the Mail API for sending notifications.
Python Runtime
We’ve updated the Python 2.7 interpreter to Python 2.7.5, which was recently released by the Python community and includes a number of bugfixes from Python 2.7.3 and Python 2.7.4.
Java WTP Tooling Support
Based on feedback from developers we have updated the Google Plugin For Eclipse to fully support the Eclipse standard Web Tools Platform and java EAR files. This system will be familiar to many Java developers as it is the most common pattern used in Eclipse for on premise and cloud environments. With WTP, EAR Files and Maven support, Eclipse users can now enjoy the full ecosystem of Eclipse plugins from the open source community.
Please check out the documentation and download the latest GPE update.
The complete list of features and bug fixes for App Engine 1.8.2 can be found in our release notes.
If you’re looking to stay up to date with the latest Google Cloud Platform news, we suggest signing up for our monthly newsletter.
- Posted by Chris Ramsdale, Product Manager
.png)
0 comments:
Post a Comment