Future of Database

One of the most interesting talks I went to at Oracle Open World last week was a talk by Noel Yuhanna of Forrester on The Future of Database Technology: An Analyst’s View.

Features and Technologies

First of all the features and technologies that he expects to become the focus of database vendors in
the immediate future are open source, consolidation, in-memory databases (caches), very large databases (apparently the largest one at the present is 50 TB), grid architecture, unstructured data, higher performance, increased availability, database security, and archiving and retention.

DBAs

An interesting fact is that apparently there are 265,000 DBA’s around the world.  An even more interesting statistic is that each DBA manages on average a terabyte of data.  I validated this statistic myself chatting to a couple of folks who turned out to be DBAs.  For example, I chatted with a very interesting person from the Liquor Licensing Board (LLB) of British Columbia, and he said that the LLB managed about 2.5 TB of data, and employed two senior DBAs and a junior consultant DBA.  This is pretty close to the 2.5 DBAs you would expect for 2.5 TBs of data.

Over the next few years Noel expects that DBA’s will spend a decreasing amount of time on tuning and performance, availability and disaster recovery, because these areas are being increasingly automated.  RDBMSs are becoming increasingly adaptive, so they they can diagnose and solve their own problems and tune themselves.   This means that instead of spending their time on administration and tuning they will spend an increasing proportion of their time on security, performance, and functionality. 

By 2012 DBAs will be spending a lot of their time on architecture and implementation to support database virtualization.

Database Virtualization

Noel outlined a very general architecture for database virtualization that includes a cache layer (forDatabasevirtualization_1
performance), a database management layer (for backup/recovery, transaction management, and other administration tasks), and the data layer itself.  To me this is a very general data management architecture that has been proven over and over again for OLTP  (online transaction processing) applications and it appears to be evolving into the de facto architecture for database virtualization.

Geoff Zeiss

Geoff Zeiss

Geoff Zeiss has more than 20 years experience in the geospatial software industry and 15 years experience developing enterprise geospatial solutions for the utilities, communications, and public works industries. His particular interests include the convergence of BIM, CAD, geospatial, and 3D. In recognition of his efforts to evangelize geospatial in vertical industries such as utilities and construction, Geoff received the Geospatial Ambassador Award at Geospatial World Forum 2014. Currently Geoff is Principal at Between the Poles, a thought leadership consulting firm. From 2001 to 2012 Geoff was Director of Utility Industry Program at Autodesk Inc, where he was responsible for thought leadership for the utility industry program. From 1999 to 2001 he was Director of Enterprise Software Development at Autodesk. He received one of ten annual global technology awards in 2004 from Oracle Corporation for technical innovation and leadership in the use of Oracle. Prior to Autodesk Geoff was Director of Product Development at VISION* Solutions. VISION* Solutions is credited with pioneering relational spatial data management, CAD/GIS integration, and long transactions (data versioning) in the utility, communications, and public works industries. Geoff is a frequent speaker at geospatial and utility events around the world including Geospatial World Forum, Where 2.0, MundoGeo Connect (Brazil), Middle East Spatial Geospatial Forum, India Geospatial Forum, Location Intelligence, Asia Geospatial Forum, and GITA events in US, Japan and Australia. Geoff received Speaker Excellence Awards at GITA 2007-2009.

View article by Geoff Zeiss

Be the first to comment

Leave a Reply

Your email address will not be published.


*