It would mean that something is really wrong with all cloud options if many people do that. And it would mean that there's a space for a cloud option that combines all good things. I really hope that I won't have to do any balancing of that kind when my app grows. I want ti all to be easy, straightforward and fairly priced, so I can focus on more important stuff. And it's what drives people to that service.
On May 11, 12:12 pm, Tim <meer...@gmail.com> wrote: > Or integration across clouds - I anticipate more people taking the user > account/authentication of GAE, putting their static files on one or more > CDNs, using 3rd party pub-sub services for updates to clients, perhaps > federating data across different services (hot data vs reference data), > keeping fixed dedicated instances for background processes that don't suffer > traffic surges etc. I'd expect to see abstraction services - libraries that > let you write to one API for a type of service and provide independence from > any specific underlying platform. > > GAE was shaping up as a nice way to seduce developers over to all sorts of > Google APIs and platforms as de-facto standards (cf Microsoft encouraging > desktop developers in the 90s) but that no longer seems to be the intention. > I sincerely hope that this isn't just in reaction to abuse of the platform > by some, abuse that might be addressed in different ways. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. 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.
