Karel,
I would inch in to it with some testing so you can get a sense of price, scale, and performance.
Consider using GAE as a Proxy, for your game first. You might round robin a portion of the traffic off to it with load balancing at the DNS level. (this would be good to figure out anyway, since you are going to lose your China, (and based on my experience some of Korea) audience do to export, firewall, and other rules)
Once you have a proxy in place on Appengine, you can get a sense of the Bandwidth and scaling costs, with minimal work converting the game code. If these costs are inline with your expectations, then start looking at some of your common SQL calls and how they map to GQL to see if those costs and speed will be with in your tolerances.
-Brandon
Brandon Wirtz |
| |||
| ||||
--
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/-/OAB-cvkIXMYJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.