*Cloud DB*
Peter Gassner

Why install and operate Oracle, MYsql, SQL server or DB2 when you can
connect to something that would do a better job faster for less money?  All
types of software are moving to cloud computing, but there has been no
serious attempt yet to move traditional relational databases from software
to a service. Why is this?  Will it ever happen?  If it does happen, what
might this "Cloud DB" look like?

This talk will focus on:

- Requirements. What market segments would be most/least receptive to Cloud
DB?

- Compelling features. Cloud DB is a combination of hardware, database type
software, and automated DBA type services. It is a big problem to solve.
What should Clould DB look like?  How would it be different from the
traditional relational databases we know today?

- Rearranging the database ecosystem.  The ecosystem today is multi layered
and built on standards.  From hardware to operating system, to database, to
business applications, to operating those applications.  The very early
implementations of cloud based services are not built on open standards.
Some standards for interoperability must develop to allow for efficiencies
and specialization.  What are these standards likely to look like and what
do they mean for the database ecosystem?


My background is pretty suited to this talk. I worked on DB2 early in my
career, then went into application platforms  being responsible for the
PeopleSoft platform and then the salesforce.com platform. During the last 2
years, I have built Veeva Systems into a 40 person profitable company by
building an industry specific application ontop of the
force.cominstrastructure.  Its been very interesting to build an
application company
on someone elses platform as a service. I know what is out there, what the
issues and opportunities are and what an application developer wants.