Magic Quadrant for Operational Database Management Systems
12 October 2015 ID:G00271405
Analyst(s): Donald Feinberg, Merv Adrian, Nick Heudecker, Adam M. Ronthal, Terilyn Palanca
The operational database management system (DBMS) market is concerned with relational and nonrelational database management products suitable for a broad range of enterprise-level transactional applications. These include purchased business applications, such as those for ERP, CRM, catalog management and security event management, and custom transactional systems built by organizations' own development teams. Also included in Gartner's definition of this market are DBMS products that support interactions and observations as new types of transaction.
Gartner defines a DBMS as a complete software system used to define, create, manage, update and query a database. A database is an organized collection of data that may be in multiple formats and may be stored in some form of storage medium (which may include hard-disk drives, flash memory, solid-state drives and/or DRAM). Additionally, according to Gartner's definition, DBMSs provide interfaces to independent programs and tools that both support, and govern the performance of, a variety of concurrent workload types. There is no presupposition that DBMSs must support the relational model or that they must support the full set of possible data types in use today. Furthermore, we do not stipulate that the DBMS must be a closed-source product; we include commercially supported open-source DBMS products in this market. Operational DBMSs must, however, include functionality to support backup and recovery, and have some form of transaction durability — although the atomicity, consistency, isolation and durability (ACID) model is not a requirement.
Operational DBMSs may support multiple delivery models, such as stand-alone DBMS software, certified configurations, cloud (public and private) images or versions, and database appliances (defined in Note 2). These are discussed and evaluated together in the analysis of each vendor.
For the purposes of this Magic Quadrant, we treat all of a vendor's products as a set. If a vendor markets more than one DBMS product that can be used as an operational DBMS, we describe each product in the section specific to that vendor, but we evaluate all of that vendor's products together as a single entity. Strengths and Cautions relating to a specific offering or offerings are also noted in the individual vendor sections. It may be important for organizations to evaluate different offerings from the same vendor separately as the portfolio of choices becomes broader, and as purchasers more frequently pursue best-fit engineering strategies.