Unfortunately, it's not the import/export that I think is keeping many from jumping headfirst into this. It's the thousands of lines of SQL written into working apps that become useless and have to be rewritten using a completely different paradigm. I just can't get myself to make that leap. I really hope that some sort of relational db support becomes reality soon.
Jeff On Dec 15, 9:56 am, Vince Bonfanti <[email protected]> wrote: > For maximum scalability on GAE you shouldn't use H2, but will want to use > the GAE datastore directly. I'm not sure that's it's really possible to do a > comparison to SQL Server, because they're really two different things. You > can think of the entire GAE infrastructure--including the datastore--as > being essentially infinite. As soon as you deploy your application, the GAE > infrastructure has essentially unlimited capacity to grow as much as your > application needs, without you having to do anything else. This is one of > the great promises of cloud computing. > > Yes, the GAE datastore is proprietary. However, Google provides tools for > datastore import/export (though I've never used these), and I'm sure > third-parties will come up with solutions. > > Vince > > On Mon, Dec 14, 2009 at 7:09 PM, Jason King <[email protected]> wrote: > > Hi Guys, > > > How can I expect this to scale as compared to SQL Server? The only thing > > that scares me about GAE is mostly the datastore/database connectivity and > > how proprietary it seems. I know it's probably a bit more costly to scale > > SQL Server, but I'm pretty confident with it. > > > -jason > > -- Open BlueDragon Public Mailing List http://www.openbluedragon.org/ http://twitter.com/OpenBlueDragon mailing list - http://groups.google.com/group/openbd?hl=en !! save a network - please trim replies before posting !!
