Google Cloud SQL, a web service that allows you to create, configure, and use relational databases with your App Engine applications is a fully-managed service that maintains, manages, and administers your databases, allowing you to focus on your applications and services.
It powers your App Engine applications with a familiar relational database (MySQL) in a fully-managed cloud environment. This allows for high data portability and helps in faster time-to-market because you can quickly leverage your existing database (using JDBC and/or DB-API) in your App Engine application.
To ensure that your critical applications and services are always running, Google Cloud SQL replicates data to multiple geographic regions to provide high data availability.
Since the preview launch in October 2011, Google has been busy working on improving the performance, adding features like scheduled backups, and multihoming to increase availability and improve performance. Also, in March this year, Google welcome its 10,000th developer on Google Cloud SQL.
Google now offering more powerful instances with up to 4GB of RAM. In addition, the company has announced a two-tier pricing plan to Cloud SQL that will be enabled on June 12th, with two options to choose from:
- "If you're a business building lightweight applications or just want to try out the service, the flexible "per use" pricing option is for you. For example, you can get started with a cloud hosted MySQL database for around a dollar per month. You pay for just what you use.
- If you're a business building heavy-traffic applications, we offer pricing packages, which are more economical and help you predict costs in advance," informs Google.
Google Cloud SQL is currently in limited preview. If you want to give us a try, start here.
Also, Google AdMob Ads SDKs for iOS and Android today received some update features including several minor bug fixes and improvements.
"We are also releasing an optional version of our SDK for iOS that includes the UDID parameter, which is used to improve ad performance and relevance. Apps utilizing this version must obtain appropriate user consent for sending device identifier information in compliance with relevant iOS policies," posted Chrix Finne, Product Manager.
You can find the updated AdMod Ads SDKs here.
Google also released today "AdWhirl v3.2" that bringd along with support for the latest and greatest from several ad networks. In particular:
- Support for AdMob v6.0.1
- Support for Millennial v4.5.1
- Support for InMobi v350
- Support for AdMob v6.0.4
- Support for Millennial v4.5.5
- Support for InMobi v350
Finally, Google announced that at the end of 2011 the Google Analytics Core Reporting API as a replacement for the Data Export API.
that as the 6 month deprecation period for the Google Analytics Core Reporting API replacing the Data Export API is nearing -- soon, Data Export API version 2.3 queries will return a v2.4 response. "If you haven't already moved to new APIs, you must do now to get movin' or risk your application not working come June."
To help make your transition faster and easier, Google published a new, easy to follow migration guide to help ensure your application continues to work after the Data Export API shut down sometime in June.
"If you are building a new application, we highly recommend using the Core Reporting API v3.0. For existing applications, we also recommend moving to v3.0 but it may be easier for you to migrate to v2.4 as an intermediary step, since it is backwards compatible with the Data Export API v2.3," posted Pete Frisella, Google Analytics API team.
Also, if you make the move to v3.0, you'll be able to take advantage of any new features, and the compact JSON format that reduces response size by 10x!
To get started, check out the Migration Guide: Moving from v2.3 APIs to v2.4 & v3.0.