( Personally I believe Google is on fire on Oracle which is the Information company for 30 years and is entirely newish in its Data design strategies. The objects will be created on the fly, as opposed to SQL, which takes a huge time on the name of normalization bullshit, and the modifications to table structures happen on the fly with expando, as opposed to RDBMS, which needs a Database Mgr's approval cycle in the industry, etc )
Business wise, one should be conscious of shifting technologies, and if people are more towards RDBMS, they should consider the Oracle's In- Memory Times Ten-series databases and force their RDBMS vendors to implement these on-the fly operations. Because precautions should be taken before the knowledge migration by the techies happen. Once Appengine folks release their SQL implementation and the RDBMS people ( Including Oracle ) migrate their data to appengine servers, You all lose the flexibility of data privacy and locations of your data servers. Instead of falling pray to that dependency, other RDBMS vendors must opt to implement their RDBMS in today's languages ( V V H L Languages ) right from the heart, so that one would be confident of supporting them over the following years. ( Inviting criticism, comments on my view. ) -- 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.
