LinkedIn Twitter
Director, OpenShift Strategy at Red Hat. Founder of Rishidot Research, a research community focused on services world. His focus is on Platform Services, Infrastructure and the role of Open Source in the services era. Krish has been writing @ CloudAve from its inception and had also been part of GigaOm Pro Analyst Group. The opinions expressed here are his own and are neither representative of his employer, Red Hat, nor CloudAve, nor its sponsors.

2 responses to “ Salesforce’s New RDBMS as a Service Offering”

  1. schultzter

    I haven’t look at the API’s at all, but vis-a-vis Oracle, as long as the backend is transparent they could always swap one for another and we’d be none the wiser.

    One thing I don’t see though, and haven’t seen anywhere, is specifying geographical location of the physical data (except maybe kind of from Amazon). If I want to build an application that can store personal information my users are going to want (should want) to know where that data is stored and what national laws are applicable to it. For example, no matter how good an investment portfolio analyser is I’m not going to upload all my transactions to it if the data is stored where a gov’t can issue specious warrants to access that information!