Ok, so an abstraction layer is the way to go. Could I be so bold ask what Google's plans are for SQL in GAE for Business? Are we talking about a separate off-the-shelf SQL back-end? Or will it be somehow integrated into Datastore/BigTable paradigm? Will SQL services be accessed via the GAE in its current form i.e. using the request-response paradigm? Or will it be via a completely different compute engine in the virtual server mould?
Just curious :-) On Aug 3, 7:39 pm, "Ikai L (Google)" <[email protected]> wrote: > There's a lot of work being done in the open source communities to try to > address the need for easier to scale structured data: > > Beyond the key-value stores: > > http://drizzle.org/http://www.mongodb.org/ > > I'd suggest looking at this projects (amongst others) and even > contributing. > > > > On Tue, Aug 3, 2010 at 7:46 AM, rvjcallanan <[email protected]> wrote: > > I understand that Google is intending to introduce an SQL back-end in > > GAE for Business. This is good news but there may also be an > > opportunity here to do more than just bolt on SQL for the sake of the > > die-hards amongst us. > > > I am wondering if Google can come up with an SQL implementation (or > > abstraction layer) which has the high scalability and high concurrency > > potential of the DataStore but with the following stipulation: > > > The number of SQL database/schema instances can grow indefinitely but > > each instance will have practical size and concurrency limits. > > > It might even be possible to store SQL instances as transaction-safe > > and data-consistent "entity groups" within the existing Datastore > > paradigm. > > > Such a high scalability SQL model would support applications which > > manage "chunks" of SQL-based data which are independent of each other > > with each chunk accessed by a limited number of users (typically one). > > There would have to be some application mechanism for imposing > > practical size limits on each chunk e.g. a housekeeping or archive > > operation. > > > There are many real world cases which could work within these > > restrictions and SQL would be a boon to rapid application development, > > schema-based data consistency and running complex queries and reports. > > > -- > > 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]<google-appengine%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-appengine?hl=en. > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > Blog:http://googleappengine.blogspot.com > Twitter:http://twitter.com/app_engine > Reddit:http://www.reddit.com/r/appengine -- 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.
