By Navneet Joneja, Product Manager for Google Cloud SQL
Cross-posted from the Google App Engine Blog
One of App Engine’s most requested features has been a simple way to develop traditional database-driven applications. In response to your feedback, we’re happy to announce the limited preview of Google Cloud SQL.
You can now choose to power your App Engine applications with a familiar relational database in a fully-managed cloud environment. This allows you to focus on developing your applications and services, free from the chores of managing, maintaining and administering relational databases.
Google Cloud SQL brings many benefits to the App Engine community:
- No maintenance or administration - we manage the database for you.
- High reliability and availability - your data is replicated synchronously to multiple data centers. Machine, rack and data center failures are handled automatically to minimize end-user impact.
- Familiar MySQL database environment with JDBC support (for Java-based App Engine applications) and DB-API support (for Python-based App Engine applications).
- Comprehensive user interface for administering databases.
- Simple and powerful integration with Google App Engine.
Cloud SQL is available free of charge for now, and we will publish pricing at least 30 days before charging for it. The service will continue to evolve as we work out the kinks during the preview, but let us know if you’d like to take it for a spin.
Navneet Joneja loves being at the forefront of the next generation of simple and reliable software infrastructure, the foundation on which next-generation technology is being built. When not working, he can usually be found dreaming up new ways to entertain his intensely curious one-year-old.
Posted by Scott Knaster, Editor
Shoot, now I want to spend the rest of the day trying to get a stock Wordpress install working through Quercus using the new Cloud SQL.
ReplyDeleteRight solution, NOSQL is next one :)
ReplyDeletedifficult to trust Google's pricing. I have been burnt once with Google app engine suddenly increasing the prices 10 fold. I dont think I am ready to fall for this this time. Thanks Google
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteyeah, look at google maps and earth enterprise pricing, "Starts at $10,000", nice to know, thank you, maybe later, much later...
ReplyDeletehttp://blog.programmableweb.com/2006/06/13/google-maps-goes-enterprise/
GAE is seducing, promising you all this and all that...from someone who has been in the trenches, at least for B2B, saying GAE sucks is an understatement.
ReplyDeletedont use gae
Dont Use Gae
DONT USE GAE
Why don't you give support for PostgreSql ? At least it does not corrupt its tables like mysql.
ReplyDeleteGreat work guys- this is BIG.
ReplyDeleteit's a great idea, but i'd rather have postgresql
ReplyDelete-d
"Why don't you give support for PostgreSql ? At least it does not corrupt its tables like mysql."
ReplyDeleteIt isn't really MySQL, it just looks like MySQL. If tables are getting corrupted, that is a severe bug, that you should report if you are in the preview.
I LOVE Google. But after the pricing shenanigans you all pulled with GAE my dreams of an application going gangbusters won't include any G-architecture.
ReplyDeleteThats GREAT NEWS! But How is it possible? What about the stuff that the datastore must be OO to be scalable?And now... it's possible!!! I'm too curious, i need to know what is the black magic?I know a hundred reasons that the datastore must be OO. But now it's simple, you can use SQL with INNER JOIN... How you will make it be scalable as now a days?
ReplyDeletePostgreSQL is much nicer and more logical, not to mention ISO SQL compliant. MySQL should be left to die.
ReplyDeleteWhile you can use use Google Cloud SQL with applications that do not use high replication, doing so might impact performance.
ReplyDeleteIf high replication database is going to be synchronously data across data centres & master-slave replication system asynchronously replicates data to other data centers as you write it. HRD is a highly available, highly reliable storage solution, but how come better performing with synchronous replication??
Argh! MySQL interface!?!? Hosted MySQL?!? Gah!
ReplyDeleteAfter years of loving PostgreSQL, this just sounds like a huge step backwards....
Looks interesting - but what about enterprise usage and functionalities such as transactions or stored procedures ?
ReplyDeleteI mostly use PostgreSQL - the question is whether this service will allow me to replace PostgreSQL, or it is only dedicated for small solutions ?
This is big....but....we do not know the pricing....GAE is one example where developers spent tons of times in it and get sucked in....but when the pricing come out , it's not affordable
ReplyDeleteDoes it work with JDO? If yes, where could i found documentation to do so.
ReplyDeleteMicrosoft has had SQL Azure for ages so why would you need this?
ReplyDeleteHi Abhishek - While we don't officially support any JDO implementations, our JDBC driver should allow you to use most of them.
ReplyDeleteHi Amit - HR allows us to keep your instance close to your application, thus improving performance by lowering the latency between the app and the database.
ReplyDeleteI'm very happy with this news. But, i can run django with cloud sql without workarounds? :D
ReplyDeletePlease remove the misleading buzzword "Cloud". What's the point behind MySQL instance? I could purchase a virtual host and install MySQL myself. You don't offer scalability features anyway (like GridSQL or pgproxy).
ReplyDeleteSupporting MYSQL is solely for the purpose of keeping Oracle/SUN at bay.
ReplyDeleteUseful for porting existing SQL apps to appengine
ReplyDeleteSo will Django work out of the box now?
I'm not looking into this unless pricing details will be unveiled. This is the problem with a lot of cloud providers. The cloud is hot, everything is in beta without future pricing details.
ReplyDeletethis is not mysql. cloud SQl is using other database drivers because its NOT mysql, its just an SQL compliant interface to BigTable. the only reason you can use mysql on the development server is because the sql drivers db-api and jodbc both support mysql so you can run it locally.
ReplyDeleteI can't believe that nobody is asking for support for FirebirdSQL, the most decent database engine out there in the open source world. Also, it is REAL open source, has triggers, procedures, updatable views, recursive procedures. I can't think of any development need that was unable to meet with FirebirdSQL. It also offer native JDBC. I suppose Google is powerful enough to give you any database to choose from! I suspect somebody at G thought that She/He was reinventing the wheel with the datastore, except She/He didn't find a way to implement joins and decided to sell the world that "joins" were a thing of the past... along with text searches and stuff like that.
ReplyDeletehi Navneet, can you contact me as I would like to share some ideas with you regarding partnering google with the concept, my contact information is smehta@raascorporation.com. I would like to talk further on this.
ReplyDeletethank you
We want MongoDB! :-)
ReplyDeleteHi how many days google take to approve my request. its horrible. i dont like to wait for 2 to 3 days.
ReplyDeleteplease approve my request for cloud sql as my boss is behind me asking the status. make some automatic approval process for this and let me know pricing details for cloud sql.
ReplyDeleteHi,
ReplyDeleteWe need to access Cloud SQL DB from external server ( Other than GAE). Please implement it also.
I have done some example application with Cloud SQL. Try them..
http://cnapagoda.blogspot.com
Thank You
Thanks Ok. It works.
ReplyDeleteGod please accept my google sql.Eagerly waiting to create my first app in google sql.
ReplyDeletedoes google support dotnet?plz who used google cloud sql suggest me?
ReplyDeletethanq