RSS | Archive | Random

About

Click for Bio

Alberto Escarlate is:

- Co-founder at Sojo Studios
- Partner at Next Generation (startup incubator)
- CTO, co-founder at TigerTag
- Faculty at Parsons New School of Design

Twitter: @cacheop


View Alberto Escarlate's profile on LinkedIn

TigerTag

YellowPin

Twitter

My shared items in Google Reader




Following

20 February 09

NRDBMS

Some customs are sometimes hard to let go. Joe Gregorio from the Google AppEngine team arguments that traditional relational databases are not the solution for every application. If you’re building on the cloud perhaps the best way to build truly scalable and distributed apps is to use datastores like the one GAE offers (based on the famous Bigtable) or SimpleDB from Amazon (AWS) - Microsoft Azure hasn’t offered anything like that what they do is a subset of SQL Server

Other than cultural resistance what other reasons would you list for not jumping off MySQL/Oracle/etc into a NRDBMS?

I can point one (at least on to GAE and AWS):  your application becomes so dependent from your cloud provider that makes it too hard to switch ‘vendors’ - if god-forbid you have that need. The cloud platform APIs are stil l proprietary and I haven’t heard any effort of standardization.

We’ve been using MySQL on EC2 for a while now and it’s somewhat comfortable to know that if we need to move out of EC2/S3 it would be ‘almost’ straightforward. Maybe that’s what Google, Amazon and other cloud hosting providers need to address moving forward.

Google App Engine Blog: Back to the Future for Data Storage

Comments (View)
blog comments powered by Disqus
Themed by Hunson. Originally by Josh