- Remember that the AppEngineDriver only works within AppEngine or the development server part of the AppEngine Java SDK. The JDBC Driver should be used in Server side code that talks to the GWT frontend code.
- JDBC-based ORM frameworks like hibernate (http://www.hibernate.org/) should generally work with Cloud SQL.
- Google Cloud SQL is ideal for small to to medium-sized applications.if we talk about scalability in terms of data volume and traffic, which breaks down into reads and writes. In case of data volumes instances are explicitly capped at 10G right now, that will increase, but when and what price it is not known. Also to overcome the data volumes people can do horizontally partitioning of data across multiple cloud sql instances(Ex. Hibernte provide sharding libraries). In second case that is Traffic a well tuned cloud sql server can easily serve it.
- One of the attracting feature of Google Cloud SQL is console UI. From this interface you can allow multiple GAE apps to access your instance. Using this console you can use MySQL grants mechanism for fine-grained control of the databases and tables within the instance. Also you can use it to give individual users access to your instance and control their access rights.
- One important limition with Google Cloud SQL is Request Timer, around 60 seconds a request handler have to generate and return a response. Once it is reached a com.google.apphosting.api.DeadlineExceededException exception occurs and request handler is interrupted.
- Also Google Cloud SQL currently not supports some of the MySQL features like user defined function and MySQL replication. It also not supports some SQL commands like LOAD DATA INFILE, SELECT ... INTO OUTFILE, SELECT ... INTO DUMPFILE, INSTALL PLUGIN .. SONAME , UNINSTALL PLUGIN, CREATE FUNCTION ... SONAME . Also function like LOAD_FILE() are also not available.
More stories on Google CLOUD SQL
No comments:
Post a Comment