One additional consideration with Cloud SQL is that you only pay for the instance while it is being accessed. If you only use your database for a few hours per month then you will only pay for those hours (at $0.10 per hour for a D1 instance).
Joe On Tuesday, May 22, 2012 3:53:22 PM UTC-7, Suyog wrote: > > Hi > > I am trying to compare costs involved in using these storage options. I am > summarizing what I know > > For datastore as per https://developers.google.com/appengine/docs/billing > writes are charged $0.10 per 100k operations and reads at $0.07 per 100k > operations. Each high level operations can cause multiple low level > operations and the number is well defined. > You get free quota. > I read somewhere that datastore scales better though that might depend on > the application. > > For cloud SQL as per https://developers.google.com/cloud-sql/docs/billing > IOs are billed $0.10 per Million and they won't say how many IOs given > query will make (packages make the whole thing cheaper) > You get additional free caching managed by MySQL > You need to make per month commitment of about $45 (I wish they had > something like tier D0 with much lower cost and resources) > > storage costs are same. > > Please let me know if I there are other considerations. > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/fHEvC20xmeYJ. To post to this group, send email to google-appengine@googlegroups.com. To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
