A report on tech crunch has confirmed that Google Cloud SQL now supports native MySQL connections, a move that is intended to make it easier to integrate third-party applications. With the support, native MySQL apps can be plugged into Cloud SQL, allowing the customer to leave system administration and management for Google.
Through MySQL Wire Protocol, the standard connection protocol for MySQL databases, Google maintains that CloudSQL allows for low latency connections for applications running on Google Compute Engine and Google App Engine. Customers can use popular tools such as MySQL Workbench, Toad and the MySQL command-line tool to manage Cloud SQL instances. It also supports standard drivers, such as Connector/J, Connector/ODBC, and Connector/NET.
The native connectivity also means that data can be replicated with control over managing and deploying cloud databases. For example, Google notes in its post that data can be replicated between Cloud SQL and on-premise databases — including Oracle, SQL Server, and DB2.
The support demonstrates how connectors like MySQL Wire Protocol will help create transparency between cloud services and any on-premise application. It’s a service that should attract those looking for the level of managed services that Google provides.
Google is starting to offer features that Amazon Web Services (AWS) has had for a few years. While Google launched the core of its CloudSQL service in June, AWS launched its MySQL service in 2009 and in 2012 began offering support for Oracle Database.
Then there is the pricing. According to the InfoQ blog, AWS RDS is “cheaper than corresponding Google Cloud SQL pay-per-hour options, but one needs to consider other costs such as data storage and transfer fees, etc.”
A report on tech crunch has confirmed that Google Cloud SQL now supports native MySQL connections, a move that is intended to make it easier to integrate third-party applications. With the support, native MySQL apps can be plugged into Cloud SQL, allowing the customer to leave system administration and management for Google.
Through MySQL Wire Protocol, the standard connection protocol for MySQL databases, Google maintains that CloudSQL allows for low latency connections for applications running on Google Compute Engine and Google App Engine. Customers can use popular tools such as MySQL Workbench, Toad and the MySQL command-line tool to manage Cloud SQL instances. It also supports standard drivers, such as Connector/J, Connector/ODBC, and Connector/NET.
The native connectivity also means that data can be replicated with control over managing and deploying cloud databases. For example, Google notes in its post that data can be replicated between Cloud SQL and on-premise databases — including Oracle, SQL Server, and DB2.
The support demonstrates how connectors like MySQL Wire Protocol will help create transparency between cloud services and any on-premise application. It’s a service that should attract those looking for the level of managed services that Google provides.
Google is starting to offer features that Amazon Web Services (AWS) has had for a few years. While Google launched the core of its CloudSQL service in June, AWS launched its MySQL service in 2009 and in 2012 began offering support for Oracle Database.
Then there is the pricing. According to the InfoQ blog, AWS RDS is “cheaper than corresponding Google Cloud SQL pay-per-hour options, but one needs to consider other costs such as data storage and transfer fees, etc.”
A report on tech crunch has confirmed that Google Cloud SQL now supports native MySQL connections, a move that is intended to make it easier to integrate third-party applications. With the support, native MySQL apps can be plugged into Cloud SQL, allowing the customer to leave system administration and management for Google.
Through MySQL Wire Protocol, the standard connection protocol for MySQL databases, Google maintains that CloudSQL allows for low latency connections for applications running on Google Compute Engine and Google App Engine. Customers can use popular tools such as MySQL Workbench, Toad and the MySQL command-line tool to manage Cloud SQL instances. It also supports standard drivers, such as Connector/J, Connector/ODBC, and Connector/NET.
The native connectivity also means that data can be replicated with control over managing and deploying cloud databases. For example, Google notes in its post that data can be replicated between Cloud SQL and on-premise databases — including Oracle, SQL Server, and DB2.
The support demonstrates how connectors like MySQL Wire Protocol will help create transparency between cloud services and any on-premise application. It’s a service that should attract those looking for the level of managed services that Google provides.
Google is starting to offer features that Amazon Web Services (AWS) has had for a few years. While Google launched the core of its CloudSQL service in June, AWS launched its MySQL service in 2009 and in 2012 began offering support for Oracle Database.
Then there is the pricing. According to the InfoQ blog, AWS RDS is “cheaper than corresponding Google Cloud SQL pay-per-hour options, but one needs to consider other costs such as data storage and transfer fees, etc.”