Thanks Nick Milon for the reply. I am right now trying to build my app so that the only thing that can be affected if GAE becomes a bad choice is just my DB layer. But that isn't too bad. The worst would be migrating data from any cloud provider to another one. But I am going to go out on a limb to say that I have some faith that Google will make it okay for us small Python developers in the future :)
Jonathan C. On May 13, 2:44 pm, nickmilon <[email protected]> wrote: > Well this is hard to answer. > Things look very liquid right now especially for python apps. > IMHO that you wait a little till all the dust, raised of new pricing > model and infrastructure (scheduler etc.) changes, settle. > Only then we will have a clear view of which way we are heading. > Also lot depends on what type of apps you have in mind. > > Take care :-) > Nick Milon > > On May 12, 10:02 am, Jonathan Chen <[email protected]> wrote: > > > > > > > > > Hey guys, > > > I am about to develop three new apps that range from small, medium, > > and large. (I'm a Python developer) > > > Knowing the price changes now would you guys still recommend that I > > build things in Google App Engine? > > > What other benefits do we get for having GAE? > > > Migrating any application from one cloud to another cloud is still > > very difficult, and never an easy job. Any cloud infrastructure then > > becomes somewhat vendor lock-in. Though GAE's datastore API' take more > > time to migrate over. > > > Jonathan C. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
