1970
Codd publishes the relational model
E. F. Codd described organizing data as relations and separating the logical model from storage details. The model became the foundation for table-based database design.
Data and AI
How the field of a Database Administrator got here: the sourced milestones from every published course of this career, on one axis.
1970 to 2025
312 milestones across 35 courses
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
26 milestones
1970
E. F. Codd described organizing data as relations and separating the logical model from storage details. The model became the foundation for table-based database design.
1970 Jun
The paper separated a logical relational view from physical storage representation. That abstraction became the SQL-side foundation later distributed systems sought to preserve.
1974
IBM documented System R as a relational approach to database management. Its work helped establish the practical path from relational theory to DBMS implementation and SQL.
1976
Chen presented entities, relationships, and diagramming as a way to capture semantic information for database design. The model gave designers a conceptual representation before table definitions.
1976 Jun
IBM published System R with authorization, integrity assertions, logging and recovery, and shared-update consistency. These capabilities established administration concerns alongside the relational interface.
1977 Nov 23
NBS issued DES as FIPS 46, establishing a standardized shared-key cipher for protecting sensitive computer data. Later storage products inherited the need to manage the secret key as well as the algorithm.
1978
Jim Gray documented transaction management, locking, and recovery foundations. Atomic completion became a distinct systems problem rather than a sequence of application retries.
1978 Nov
Predicate-lock work addressed conflicts involving a condition or set of rows rather than one named record. It showed that protecting a rule can require reasoning beyond individual row locks.
1979
Oracle V2 was introduced as a commercially available SQL-based relational database management system.
1979
Relational Software, Inc. released Oracle V2 as a commercial SQL-based relational database. SQL moved from research systems into a product category that competing database vendors adopted.
1979
Oracle Version 2 was released as the first commercially available SQL-based relational DBMS. Operating a relational database became a commercial platform responsibility rather than only a research concern.
1979 Jun
Crash Recovery in a Distributed Data Storage System described atomic transactions across independent computers. It made failure recovery part of the transaction contract.
1980 Mar
SDD-1 presented distributed query processing, concurrency control, failure resilience, and directory management behind a nondistributed user view.
1981 Apr
Skeen examined commit progress after failures. The work made classic 2PC blocking a defined target for later protocol designs.
1981 Nov
Kung and Robinson described optimistic methods that validate conflicts instead of reserving data for the full operation. The approach underlies version checks and retry-on-conflict designs.
1983
Oracle Version 3 became the first relational database to run on mainframes, extending the product to that operating environment.
1983 Oct
R-star explored SQL-oriented computation and communication across an experimental distributed database. It made remote data and distributed transaction management part of relational database research.
1986
ANSI published the first SQL standard. A standard core gave database products a common reference point even as their dialects continued to differ.
1986
Implementation of POSTGRES began at the University of California, Berkeley. Its later releases focused on portability and reliability, both central concerns for administrators.
1986
The Berkeley POSTGRES project began implementation. It became a long-running research and production lineage for object-relational database work.
1986
The first ANSI SQL standard established a shared language for defining and querying relational data. It made portable SQL a practical design target.
1986 Dec
R star documented Presumed Abort and Presumed Commit extensions. These reduced messages and log writes under defined common outcomes while retaining recovery rules.
1987
ISO adopted SQL as ISO/IEC 9075. The paired ANSI and ISO work made SQL an international database-language standard.
1987
POSTGRES demoware became operational in 1987 and was demonstrated at SIGMOD in 1988. The project moved from design papers into a working system.
1988 Jan
Oki and Liskov described a primary-copy method that reorganizes replicas into new views after crashes or network partitions while preserving service state.
1989 Jun
Version 1 was released to a small group of external users. The release marked an early step from academic prototype toward use outside its original project.
22 milestones
1991
Version 3 added multiple storage managers, an improved query executor, and a rewritten rule system. Those changes established several of the project areas that later PostgreSQL development continued to extend.
1991
Version 3 added multiple storage managers, an improved query executor, and a rewritten rule system. Those changes emphasized DBMS behavior beyond the table abstraction.
1991 Dec
XA defined application, transaction-manager, and resource-manager roles plus recovery interfaces. It gave interoperating resources a common vocabulary for branches and global identifiers.
1992
Oracle7 introduced PL SQL stored procedures and triggers, bringing stored program units into the database platform.
1992
ANSI and ISO published the revision commonly called SQL-92. It became a long-lived baseline for the portable syntax developers still recognize.
1992
SQL-92 revised the standard language used by relational systems. Schema design could increasingly distinguish standard declarations from vendor-specific extensions.
1992 Nov
SQL-92 established the named isolation-level vocabulary used to compare relational database implementations. It made dirty reads, nonrepeatable reads, and phantoms common contract terms.
1994
Version 4.2 was released as the final Berkeley POSTGRES release. The following work shifted toward adding SQL to the code base.
1994
Postgres95 replaced PostQUEL with SQL and was released to the web as an open-source descendant of Berkeley POSTGRES. SQL became central to this branch of the system.
1995
Developers added SQL language support and renamed the project Postgres95. The release also carried a tutorial for regular SQL features and Postgres95-specific features.
1995 May
MySQL released its first version in May 1995. It made a widely deployed database engine available to administrators outside the established enterprise database vendors.
1995 May 23
MySQL's first release established the client-server SQL database that later versions expanded. The project history identifies this as the public starting point.
1995 Jun
Berenson and colleagues showed that the ANSI phenomena did not fully characterize common isolation implementations. Testing product guarantees became more important than relying on a level name.
1996
The project adopted the PostgreSQL name and began version numbering at 6.0. A durable open-source database project created a long-lived administration surface with public documentation and releases.
1996
The project adopted the PostgreSQL name to reflect both its POSTGRES origin and SQL capability. Version numbering restarted at 6.0 in the older POSTGRES sequence.
1996
The project adopted the PostgreSQL name to mark its SQL capability and began version numbering at 6.0. The rename connected the original POSTGRES work to a continuing database project.
1996 Aug 21
HIPAA established a statutory basis for standards governing electronic health information. Its later Security Rule made information-system activity controls relevant to databases containing electronic protected health information.
1997
Oracle8 added object-relational capabilities, which established the product description still used for Oracle Database.
1998 May
Lamport's paper formalized consensus that preserves consistency through non-Byzantine failures and resumes progress when a majority operates.
1999
SQL:1999 added features including recursive queries and standardized procedural extensions. It widened SQL beyond basic table queries while retaining the relational core.
1999
SQL:1999 continued the sequence of standard revisions that database products use as a common reference for SQL behavior and declarations.
1999 Mar
RRDtool documented timestamped counters in round-robin archives with fixed retention. It made storage lifetime a property of operational measurements.
76 milestones
2000
MySQL adopted the GNU General Public License. Open-source distribution widened the set of teams that could install, configure, patch, monitor, and maintain their own database servers.
2000
Neo4j records the invention of its property-graph model in 2000. This represented a data model in which nodes and relationships are central rather than only tabular joins.
2000
Neo4j dates the invention of the property graph model to 2000. The model established nodes and relationships as first-class data for connected-domain questions.
2000 May 8
Version 7.0 implemented foreign keys and improved optimizer work. This made relational integrity and query-plan selection more central to ordinary PostgreSQL practice.
2000 Jun
D. Richard Hipp releases SQLite as a public-domain embeddable SQL library. The initial design prioritizes a zero-configuration, in-process database engine with a single-file storage model.
2000 Jul 19
Eric Brewer's PODC invited talk framed consistency, availability, and partition tolerance as a fundamental distributed-service tradeoff. It gave multi-region designers a vocabulary for behavior during network separation.
2001
Oracle9i introduced Oracle RAC, allowing multiple instances to access one database.
2001 Jan
The 3.23 series established a production release line with additional table and indexing capabilities. It marked MySQL's move beyond its earliest releases.
2001 Jun
Oracle9i Data Guard documented physical and logical standby databases, broker management, switchover, and no-data-loss protection modes.
2001 Nov 26
NIST standardized AES after selecting Rijndael through a public competition. AES became the symmetric foundation used by modern database data-encryption keys and key-wrapping systems.
2001 Dec
The shorter publication made proposer, acceptor, majority, and safety reasoning more accessible to implementers of replicated systems.
2002
NIST issued contingency-planning guidance for information technology systems. Recovery planning became an explicit system responsibility rather than an ad hoc response after loss.
2002 Jan
NIST published its Contingency Planning Guide for Information Technology Systems. It framed recovery planning as a documented operational capability rather than a storage-copy task.
2002 Jun
Seth Gilbert and Nancy Lynch published a proof in an asynchronous network model. The result made clear that consistency and successful responses on every separated side cannot both be guaranteed during a partition.
2002 Jul 30
The Act strengthened corporate responsibility and financial disclosure requirements. Database change and access evidence became part of how many organizations support internal-control assessments over financial reporting systems.
2003
Neo4j records its first graph database in continuous production in 2003. This marked an early operational use of graph storage rather than only a modeling experiment.
2003
The paper documented a distributed file system designed around large data-intensive workloads and commodity-hardware failures. It made workload assumptions a visible part of storage-system design.
2003
Oracle Database 10g introduced grid computing as the product's deployment and resource-sharing direction.
2003
SQL:2003 revised the standard SQL family. Designers and implementers continued to compare database-specific capabilities with an evolving standard vocabulary.
2003
SQL:2003 added window functions and SQL/XML work. Window functions made ranking and calculations across related result rows part of standard SQL practice.
2003 Feb 20
HHS finalized technical safeguards that include audit controls. The rule requires mechanisms to record and examine activity in systems that contain or use electronic protected health information.
2003 Mar
The 4.0 release line brought major SQL and replication development into a production series. Operators gained a more capable platform for transactional web applications.
2003 May
Brad Fitzpatrick created Memcached for LiveJournal, using spare RAM across servers as a distributed cache. The simplest expression of the key-value idea: store a value under a key, look it up later, evict when memory runs out.
2004 Jun
Version 3.0 replaces the version 2 database file format, adds support for 1, 2, 4, and 8-byte integer keys, and establishes the text encoding and typing rules that the current format inherits.
2004 Aug
Paxos Commit showed how consensus can replicate the coordinator decision path while retaining participant votes. It clarified the distinction between replicated decisions and atomic commitment.
2004 Oct
The 4.1 series added subqueries and expanded character-set support. Query authors could express more relational work inside the server.
2005
MySQL 5.0 added stored procedures, triggers, and views. Database administration increasingly had to account for behavior and dependencies held inside the database as well as server settings.
2005
PostgreSQL 8.0 documented continuous WAL archiving and replay to a selected point in time. This made a separate historical recovery path a first-class complement to a live standby.
2005 Jan
PostgreSQL 8.0 added a NOWAIT option to LOCK. Applications could choose an immediate conflict result instead of waiting on that command path.
2005 Jan
PostgreSQL 8.0 introduced point-in-time recovery and continuous backup. A base backup plus archived WAL could now recover either to failure or to an earlier transaction point.
2005 Jan
PostgreSQL 8.0 added savepoints, allowing part of a transaction to be aborted without discarding earlier work. It made partial recovery possible inside a complex unit.
2005 Jan 19
PostgreSQL gained online backup and log-based recovery to a selected point, establishing an independent recovery path beyond live replicas.
2005 Jan 19
PostgreSQL 8.0 was released as a major version. It marked a new platform era that included native Windows support and changed deployment choices for many users.
2005 Apr 20
The main compliance date arrived for covered entities, with small health plans receiving one additional year. Audit controls moved from a published requirement into an operating obligation for covered systems.
2005 Jul 6
Rails added version-controlled classes for applying schema transformations across databases. This made schema evolution part of an application framework workflow.
2005 Aug
The recommendation assembled general guidance for cryptographic key types, protection, lifecycle, cryptoperiods, compromise, and recovery.
2005 Sep
Oracle added transparent column encryption with table keys protected by a master key in a wallet. Database encryption moved from application code into a built-in key hierarchy.
2005 Oct 19
The 5.0 production series added stored procedures, views, and triggers to the server's SQL object model. More database behavior could live beside tables and constraints.
2005 Nov
PostgreSQL 8.1 introduced PREPARE TRANSACTION, COMMIT PREPARED, ROLLBACK PREPARED, and pg_prepared_xacts. Operators could inspect and complete durable prepared work.
2005 Nov
SQL Server 2005 marked a major generation of the Database Engine and its integrated services. Its release established the 2005 product line later documented in Microsoft's lifecycle record.
2005 Nov 9
PostgreSQL replaced the separate user and group model with roles that can log in, own objects, hold privileges, and inherit other roles.
2006
Google's Bigtable paper described distributed structured storage across thousands of servers. Its partitioned data model became one foundation for later globally distributed database designs.
2006
Google described a distributed storage system for structured data with a simple model and client control over layout and format. It provided a widely read example of nonrelational storage at large scale.
2006
Google's paper documented a distributed storage system for very large structured datasets and established the row, family, qualifier, and version vocabulary.
2006
HBase development began late in 2006, turning the Bigtable model into an open-source implementation for the Hadoop ecosystem.
2006
Liquibase established database-independent changelogs and tracked changesets as a dedicated change-management approach.
2006
NIST documented a forensic process for identifying, acquiring, protecting, processing, analyzing, and reporting digital evidence. Recovery involving evidence gained a preservation and documentation discipline.
2006 Sep
NIST published enterprise guidance for building log-management infrastructure and processes. Database audit records could now be placed in a broader collection, analysis, storage, and operational model.
2006 Nov
Google documented a distributed storage system that split sorted table data into tablets across commodity servers. The design made tablet splitting and movement part of large-scale structured storage.
2006 Nov
Bigtable demonstrated structured storage at petabyte scale across thousands of commodity servers. Its data model was not relational, highlighting the scale and SQL tradeoff that later systems addressed.
2007
Amazon published Dynamo, a highly available key-value store that sacrifices consistency in some failure scenarios. The paper made application-assisted conflict handling a concrete distributed-storage tradeoff.
2007
Neo4j 1.0 was released as open-source and commercial packages. The release made the native graph database available as a product developers could adopt.
2007 Oct
Werner Vogels blogged about Dynamo, Amazon's internal always-available key-value store. The paper stated the tradeoff that defines the category: give up joins, secondary queries, and strict consistency in exchange for write availability and near-linear scale.
2007 Oct
Dynamo combined partitioning, configurable replica quorums, versioned values, hinted handoff, and repair to favor availability for key-value workloads.
2007 Oct
Amazon documented a highly available key-value store using consistent-hash partitioning and replication. The design made partition placement and availability tradeoffs explicit to system designers.
2007 Oct 14
The Dynamo paper described a highly available key-value store that favored continued operation and eventual reconciliation. Its replication and conflict techniques influenced multi-active database systems.
2007 Nov 15
The guide organized storage encryption by disk, volume, and file or folder boundaries. It made threat and storage location explicit inputs to an encryption decision.
2008
Facebook open-sourced Cassandra after using it for Inbox Search, bringing a peer-to-peer design into the wide-column ecosystem.
2008
Cassandra first released in 2008 as a distributed NoSQL database. The project combined partitioned data placement with replicated operation for high-volume workloads.
2008
HBase became a Hadoop subproject, formalizing its place in the distributed-data stack.
2008
SQL:2008 added another dated revision to the SQL standard sequence. The standard remained a reference point while database engines kept their own extensions.
2008 Aug
SQL Server 2008 began the next major product generation. Version selection became an operational concern because documentation and support policies attach to particular releases.
2008 Aug 6
SQL Server 2008 brought page-level TDE into Microsoft's database engine. A database encryption key protected by a certificate or external key provider covered data and transaction-log files.
2008 Nov
Apache established CouchDB as a top-level project. Its document and replication model became an established open-source route for document-oriented applications.
2008 Nov 14
The 5.1 series made partitioning, the event scheduler, and a plugin architecture part of production operations. Database administration broadened beyond table and query management.
2009
Oracle acquired Sun Microsystems, bringing MySQL into the Oracle product portfolio. Administrators had to evaluate community and commercial MySQL distributions within one product family.
2009 Feb
MongoDB 1.0 entered the stable release schedule. It established the first versioned baseline for production support and upgrades.
2009 Feb
Salvatore Sanfilippo open-sourced Redis, originally prototyped in Tcl as a real-time log analyzer. Rewritten in C, it extended the key-value model with native data structures — hashes, lists, sets, sorted sets — and became the category's reference in-memory data structure server.
2009 Jul
Apache's release archive records Cassandra 0.3.0. It supplies a dated anchor for the open-source wide-column implementation that this course uses as a query-driven example.
2009 Aug
MongoDB launched in 2009 around a document-based data model. It made application-facing document storage a prominent database product category.
2009 Aug
Revision 3 included Audit and Accountability as a security-control family in a catalog for federal information systems and organizations. It reinforced the separation of event generation, review, protection, and related control activities.
2009 Oct
Amazon introduced RDS as a service for setting up, operating, and scaling a relational database in the cloud. It put patching, backups, and resizable capacity into the managed-service operating model.
2009 Oct
Amazon introduced RDS with automated database patching and backups for MySQL. The operational model began to divide administration between a cloud provider and the application team.
2009 Oct
Apache's release archive records CouchDB 0.10 in October 2009. The release line made the project available as a maintained Apache distribution.
2009 Oct
SQLite 3.6.19 adds foreign key constraint enforcement, activated per-connection via PRAGMA foreign_keys. The decision to keep the default off preserves backward compatibility but means referential integrity requires an explicit application choice.
2009 Oct 27
AWS introduced Amazon RDS with a managed MySQL service. Managed setup, patching, backups, and resizable capacity moved common relational database administration into the service boundary.
142 milestones
2010
The Apache archive records the 0.6 release line. Early public releases established the project as an Apache-distributed database rather than an internal system.
2010
Apache Cassandra's project history records its graduation from the Incubator in 2010. The project then became an Apache-managed implementation of a distributed database model.
2010
HBase became an Apache top-level project, establishing its independent project lifecycle.
2010
The revision updated federal contingency-planning guidance. It reinforced recovery procedures and testing as planned operational controls.
2010
Vitess moved MySQL shard routing out of YouTube application code and into a proxy and management layer. Applications could use a shared interface while the platform managed shard locations.
2010 Apr 20
Flyway introduced a plain-SQL migration tool designed to roll database changes out with application deployment across environments.
2010 May
NIST SP 800-34 Revision 1 updated federal contingency-planning guidance. It connected recovery requirements with risk management and the system development life cycle.
2010 Jul
SQLite 3.7.0 adds write-ahead logging, allowing readers to overlap with one writer instead of blocking during commit. WAL becomes the default journal mode for most production deployments, changing the concurrency boundary the entire ecosystem operates within.
2010 Sep
PostgreSQL 9.0 introduced built-in WAL streaming to standby servers and read-only queries on hot standbys. The release reduced the gap between a replicated copy and a usable read-serving standby.
2010 Sep 20
PostgreSQL could stream write-ahead log records directly to a standby, while hot standby allowed read-only queries during recovery.
2010 Sep 20
Schema-wide GRANT and REVOKE operations addressed existing objects. ALTER DEFAULT PRIVILEGES separately defined access for future objects.
2010 Sep 20
Built-in WAL streaming reduced standby delay, while hot standby allowed read-only queries during recovery and made native failover designs practical.
2010 Sep 20
Version 9.0 introduced streaming replication and Hot Standby. Those features made replica and recovery planning a more direct part of PostgreSQL operations.
2010 Oct 1
KMIP defined a common protocol for cryptographic objects and operations. Databases and storage systems gained a vendor-neutral path to external key managers.
2010 Dec 3
MySQL 5.5 made InnoDB the default storage engine. New tables therefore received transactions, row-level locking, and crash recovery unless configured otherwise.
2011
Neo4j launched Cypher as a declarative language for property graphs. Pattern matching became the main way to express graph reads and writes.
2011
Neo4j launched Cypher as a declarative language for property graphs. The milestone illustrates the growth of specialized query languages alongside SQL.
2011
SQL:2011 added temporal database features. The standard gained a common way to express time-aware data and queries.
2011
SQL:2011 continued the standard's evolution. The revision provides historical context for why relational design must separate durable logical rules from an engine's current feature set.
2011 Jan
The Apache Software Foundation announced Cassandra 0.7 as a scalable open-source distributed database. The release documented its use for large data and high query volumes.
2011 Sep
MongoDB 2.0 entered the stable release schedule. Teams on that generation had a defined support lifetime through March 2013.
2011 Sep
PostgreSQL 9.1 added streaming backups and pg_basebackup. This removed the need to manually transfer a file-system backup when setting up a standby.
2011 Sep
PostgreSQL 9.1 let a primary wait for a standby to write transaction information before acknowledging commit. HA design could then choose a stronger durability guarantee at the cost of added dependency on standby acknowledgement.
2011 Sep
PostgreSQL 9.1 replaced its prior Serializable snapshot behavior with true Serializable isolation. Its older snapshot behavior remained available as Repeatable Read.
2011 Sep
Basho Technologies shipped Riak 1.0 with secondary indexing, a MapReduce rewrite (Riak Pipe), and LevelDB backend support — the first production-ready, open-source, Dynamo-inspired distributed key-value database.
2011 Sep 12
Commits could wait for a configured standby acknowledgment, making the durability and latency boundary an explicit per-transaction choice.
2011 Oct
The Apache archive records the 1.0.1 distribution in October 2011. The 1.0 series marked a stable release line for the project's users.
2011 Nov 30
Alembic provided an initial migration environment for SQLAlchemy applications, including multiple-database support.
2012
The storage-engine history records the 1.2 format changes, including the `ib` SSTable format. Storage-format evolution matters because upgrades and data movement depend on compatible on-disk structures.
2012
The Spanner paper described a synchronously replicated, globally distributed database with externally consistent transactions. It demonstrated a coordinated alternative to eventually consistent multi-region writes.
2012
Prometheus started as an open-source project at SoundCloud. Its dimensional metric model became a common reference for monitoring time series.
2012 Jan
AWS announced DynamoDB as a fully managed NoSQL database service. The launch made service-managed partitioning and request capacity a mainstream cloud database design choice.
2012 Jan
AWS launched DynamoDB as a fully managed NoSQL service derived from Amazon's internal Dynamo, offering single-digit-millisecond latency on SSD storage with automatic partitioning. Made Dynamo's ideas accessible without operating a distributed system.
2012 Jan
AWS announced DynamoDB as a managed NoSQL database service. Managed NoSQL services became a practical deployment path alongside self-operated database servers.
2012 Jan 18
DynamoDB introduced a managed key-value NoSQL service with predictable performance and scaling. Database selection on AWS now included a service designed around key-based access patterns rather than relational queries.
2012 Mar
SQL Server 2012 extended the product line into another supported release generation. Administrators needed to align installation, upgrade, and support choices with the server version.
2012 Apr 2
Availability groups brought coordinated replicas, listener-based client routing, and planned, automatic, and forced role transitions into SQL Server.
2012 Apr 5
The release introduced a rebuilt pt-online-schema-change with replication-aware throttling for altering large MySQL tables while clients continue reading and writing.
2012 Oct
Spanner documented synchronous replication, consensus, distributed transactions, and external consistency across global placements.
2012 Oct
Google documented a globally distributed database that combined sharding with synchronous replication and externally consistent transactions. Partition placement became part of a transactional global database design.
2012 Oct
Spanner described two-phase commit across participant groups and Paxos replication within groups. It demonstrated this composition at global scale.
2013
The storage-engine history records the `ja` format for 2.0. The release line updated how SSTables recorded data and metadata while retaining Cassandra's immutable-file design.
2013
Neo4j 2.0 extended the model with labels and introduced a visual IDE. Labels gave queries and schema design another explicit structure alongside relationship types.
2013
Oracle Database 12c introduced the container database and pluggable database architecture for consolidation.
2013 Feb
Amazon Redshift brought a managed cloud data warehouse to AWS. Analytical processing became a distinct service choice from the operational database path.
2013 Feb 5
The 5.6 production series expanded InnoDB online data-definition operations and global transaction identifiers. Schema maintenance and replication gained stronger operational primitives.
2013 Mar
MongoDB 2.4 entered the stable release schedule. Its March 2016 end of life made version planning a continuing operational responsibility.
2013 Jun
The first commit to etcd's repository as part of the CoreOS project. etcd would become the primary datastore for Kubernetes when it launched in 2014, establishing the key-value model as the standard for cluster coordination and configuration.
2013 Aug
SQLite 3.8.0 introduces partial indexes, allowing an index to cover only the rows matching a WHERE expression. This reduces index storage and write overhead for queries with a consistent filter predicate.
2013 Nov
Facebook released RocksDB, forked from Google's LevelDB and optimized for flash storage with multi-threaded compaction. The embeddable LSM-tree engine that became the storage layer inside dozens of later databases and systems.
2013 Nov 26
Managed asynchronous replicas could be promoted in another Region, turning a read-scaling feature into a documented regional DR target.
2014
The revision defined clear, purge, and destroy sanitization methods. It made the boundary between sanctioned sanitization and later recovery expectations more explicit.
2014
Replication slots retained needed WAL for disconnected consumers, while cascading replication let a standby relay WAL to downstream standbys. Both changed how operators manage replica catch-up and topology fan-out.
2014 Apr
Redis 2.8.9 introduced HyperLogLog, extending the data-structure model to approximate cardinality with bounded memory. It gave practitioners a native option for count-distinct workloads.
2014 Apr
SQL Server 2014 continued the major-release cadence for the Database Engine. Version-aware operational procedures remained necessary across long-lived deployments.
2014 Jun
Raft separated leader election, log replication, safety, and membership change into components intended to support practical implementations.
2014 Aug
Microsoft introduced Azure DocumentDB in public preview as a managed NoSQL document database service. The service brought document storage and query semantics into Azure's managed database portfolio.
2014 Nov
Aurora added an AWS-built relational service compatible with MySQL. It made relational-engine compatibility and cloud-specific cluster architecture separate selection factors.
2014 Nov 12
AWS KMS introduced a managed key control plane integrated with database and storage services. Cloud workloads could use centralized keys and audit key use without operating their own HSM fleet.
2014 Dec
PostgreSQL 9.4 added replication slots that preserve WAL resources until a standby no longer needs them. This made retention behavior more explicit in log-based recovery designs.
2015
Google launched Cloud Bigtable as a managed service with an HBase-compatible API.
2015
The openCypher standards project launched to open the Cypher language to wider adoption. Cypher therefore became more than a single-product query syntax.
2015
Redis 3.0 added Redis Cluster for horizontal key partitioning. Client routing and key placement became part of application design instead of only an operational sharding concern.
2015 Jan
Prometheus 0.10 was publicly announced after internal and early-adopter use. The project then published material for a wider operations audience.
2015 Mar
MongoDB 3.0 entered the stable release schedule. The release marked the next supported branch after the 2.x series.
2015 Apr
PingCAP began building an open-source distributed SQL database to replace manual MySQL sharding while retaining MySQL compatibility.
2015 May
SQLite 3.8.3 adds ordinary and recursive common table expressions, enabling recursive graph traversal and cleaner query decomposition without subquery nesting.
2015 Jul
AWS made Aurora available for customers after its 2014 announcement. It tied a MySQL-compatible relational interface to a provider-designed replicated storage architecture.
2015 Jul 27
Aurora separated replicated storage from database instances across availability zones and used replicas as managed failover targets.
2015 Oct
AWS introduced a managed migration service for moving databases to AWS with ongoing replication. Migration planning gained a service-assisted path alongside schema conversion and application validation.
2015 Oct 21
MySQL 5.7 added a native JSON type and JSON functions. Relational schemas could hold validated document values without treating them as plain strings.
2015 Nov
Apache Cassandra 3.0 released on November 9, 2015. It began a long-lived major release line that later became an upgrade boundary for operators.
2015 Nov
Cassandra 3.0 established the major storage-engine baseline that preceded 4.0.
2015 Nov 3
MongoDB announced an encrypted WiredTiger storage engine with external KMIP support. The design separated database keys from the master key managed outside the server.
2016
MongoDB launched Atlas as its database-as-a-service offering. Document database operations increasingly became a managed-service decision rather than only a server administration task.
2016
Neo4j 3.0 added the Bolt binary protocol and native drivers alongside procedures and a cost-based query optimizer. Application connectivity and query planning became more explicit parts of the platform.
2016
NIST issued a guide for cybersecurity event recovery. Recovery planning was connected to restoring operations after a cyber event, not only storage.
2016
Redis 3.2 added geospatial commands such as GEOADD and GEORADIUS. Location lookups became another operation that could use a native Redis data type and command set.
2016
SQL:2016 incorporated JSON-related features. Relational databases could standardize some work with semi-structured values without abandoning tables, constraints, and joins.
2016 Jan 7
pg_rewind reduced the work needed to turn a diverged former primary into a standby that follows the new primary after failover.
2016 Jan 7
CREATE POLICY and row-security table controls moved per-row read and write decisions into the database authorization path.
2016 Apr 27
The European Parliament and Council adopted Regulation 2016 slash 679. Its accountability and security framework increased the need to demonstrate controlled processing of personal data, including activity in database systems.
2016 Jun
SQL Server 2016 introduced a new product generation under Microsoft's Fixed Lifecycle Policy. The release remained a distinct support and update baseline for database operations.
2016 Jun 1
SQL Server made security predicates available in the database engine so applications could centralize row filtering and write blocking.
2016 Jul
Prometheus 1.0 marked a stable API for the 1.x line. That gave monitoring integrations a clearer compatibility target.
2016 Aug
Cloud Bigtable reached general availability as a production managed service for large NoSQL workloads.
2016 Aug 1
GitHub released a triggerless MySQL online schema migration tool that follows binary-log changes and provides pause and throttle controls.
2016 Sep
InfluxDB 1.0 committed to 1.x compatibility and stabilized its storage format. This anchored a purpose-built TSDB model for telemetry deployments.
2016 Sep
PostgreSQL 9.6 allowed a replication slot to reserve WAL needed for a base backup. This reduced a gap where required log segments could disappear during backup creation.
2016 Nov
MongoDB 3.4 entered the stable release schedule. Practitioners could use its lifecycle dates to plan supported upgrades.
2016 Dec
MySQL 5.7.17 made Group Replication generally available with group membership, conflict handling, distributed recovery, and multi-primary update capability. This brought membership decisions and replication into one MySQL feature set.
2016 Dec 12
Group membership, consistency checks, and automatic primary election became built-in components for highly available MySQL topologies.
2017 Jan
An accidental deletion caused a GitLab.com database outage and unrecoverable production data. GitLab's postmortem documented the incident and follow-up work on backup monitoring.
2017 Apr
InnoDB added NOWAIT and SKIP LOCKED options for locking reads. Queue and reservation designs could explicitly fail or omit busy rows instead of always waiting.
2017 Apr
InnoDB Cluster combined Group Replication with MySQL Shell administration and MySQL Router. The bundle connected group failover with setup, management, and client routing.
2017 May
Microsoft announced general availability of Azure Cosmos DB. The service combined geographic distribution with configurable consistency and multiple data models.
2017 May
Azure Cosmos DB became generally available and existing DocumentDB customers moved to the service. Globally distributed document workloads made partitioning and consistency choices more visible in product selection.
2017 May
Google made Cloud Spanner generally available as a globally distributed relational database service. It brought SQL semantics and ACID transactions into a horizontally scalable managed service.
2017 May
CockroachDB reached a production release with SQL over distributed key ranges and replicated transactions. Its range layer split and rebalanced ordered keyspace behind a logical SQL database.
2017 May
Google's follow-up paper documented distributed query execution, resharding behavior, and Spanner's evolution into a fuller SQL system.
2017 May 10
Microsoft launched Azure Cosmos DB with global distribution and several consistency models. Managed region placement moved global topology and consistency choices into a public cloud database service.
2017 May 10
CockroachDB 1.0 made a range-based, replicated, transactional SQL system available as a production product.
2017 May 11
Groups coordinated geographic replication and supplied stable read-write and read-only endpoints that changed destination during failover.
2017 Sep
Redis 4.0 made it possible to extend Redis with modules and introduced nonblocking deletion. The server could support new data types and capabilities without putting every feature in the core command set.
2017 Oct
PostgreSQL added native declarative table partitioning with range and list strategies. Partition bounds and tuple routing became first-class database definitions rather than inheritance conventions.
2017 Oct
SQL Server 2017 brought the Database Engine to Linux as well as Windows. Deployment choice now included an operating-system boundary, not only an edition or hardware decision.
2017 Oct
TiKV 1.0 established the project's stable release line. It made the distributed key-value storage layer available as a versioned system rather than a pre-release component.
2017 Oct 5
Publication and subscription became built-in, allowing selected table changes to move independently of byte-for-byte physical standby copies.
2017 Oct 5
New roles separated access to settings, statistics, and table scans from unrestricted superuser authority.
2017 Oct 5
PostgreSQL 10 began the current major-version numbering scheme, in which the first number identifies the major release. The project now releases a major version about once each year.
2017 Oct 16
TiDB 1.0 delivered a MySQL-compatible distributed database designed for transactional and analytical processing over one architecture.
2017 Nov
Google announced general availability of Cloud Spanner multi-region configurations. The release extended synchronous replication and transactions across regions and continents.
2017 Nov
MongoDB 3.6 entered the stable release schedule. Its published end of life in April 2021 defined when that branch ceased to be supported.
2017 Nov
Prometheus 2.0 followed a redesign addressing storage bottlenecks in dynamic environments. It also connected the design to remote APIs and hot backups.
2017 Nov 29
AWS launched Global Tables as managed multi-region, multi-active replication for DynamoDB. Applications could write through regional replicas without operating their own replication layer.
2018
Oracle launched Autonomous Database as a managed database service that automates routine operational work.
2018 Feb
The Cloud Native Computing Foundation accepted Vitess as an incubation project. Sharded MySQL routing and operations gained a vendor-neutral project home.
2018 Apr
TiKV 2.0 added experimental Region Merge and a Raw DeleteRange API. Region maintenance became a more explicit operational concern as key ranges changed shape.
2018 Apr 19
MySQL 8.0 introduced a transactional data dictionary and added common table expressions and window functions. Metadata recovery and analytical SQL changed materially for practitioners.
2018 Apr 19
MySQL administrators gained named privilege collections, role grants, default-role activation, and session role selection in the 8.0 line.
2018 May
Neptune added a managed graph database to the AWS portfolio. Relationship traversal could be evaluated as a first-class data-model choice instead of being forced into tables or documents.
2018 May 25
The GDPR began applying across European Union member states. Database audit designs increasingly had to balance accountability evidence with minimization and protection of personal data inside the audit trail.
2018 Jun
MongoDB 4.0 added multi-document ACID transactions for replica sets. Data-model work could now use a transaction when one document could not express an invariant.
2018 Jun
MongoDB 4.0 made multi-document ACID transactions generally available. Practitioners could use broader transaction boundaries when an aggregate boundary did not cover a required operation.
2018 Aug
AWS introduced Aurora Serverless as a relational-database deployment option that starts, scales, and stops capacity for changing workloads. It made capacity behavior an explicit managed database choice.
2018 Aug
Regional replication added a primary-primary multi-cluster option, making routing and availability part of deployment design.
2018 Sep
SQLite 3.25.0 introduces window functions, allowing aggregate computations over a sliding frame of rows without self-joins or application-level state management.
2018 Oct
Microsoft made the Azure SQL Database Managed Instance general-purpose tier generally available. It added a managed migration path for SQL Server workloads that needed broader instance compatibility.
2018 Oct
Redis 5.0 introduced Streams as a log-like data structure with ordered entries. This created a retained alternative to transient pub/sub for event-processing designs.
2018 Oct 18
PostgreSQL 11 made it possible to avoid rewriting a table when adding a column with a non-null constant default. A frequent schema expansion became less disruptive.
2018 Nov
Aurora Global Database introduced storage-based replication across AWS Regions for global reads and regional-outage recovery. HA planning could use a managed cross-region topology with a promoted secondary writer.
2018 Nov 27
AWS announced cross-region Aurora replication with one primary and remote read replicas. The feature established a managed single-primary alternative for global reads and regional disaster recovery.
2018 Dec
The CNCF accepted etcd as an incubating project at KubeCon Seattle, with Red Hat contributing it after acquiring CoreOS. Cemented etcd's role as the default coordination store for the cloud-native stack.
2019 Jan
Amazon DocumentDB became generally available with MongoDB compatibility. Teams gained another managed option, while still needing to verify behavior required by their applications.
2019 Jan 8
DocumentDB added a managed document database with MongoDB compatibility. Compatibility testing became an explicit part of selecting a managed document target.
2019 May
Global replication extended the service to multi-region deployments and independent cluster scaling.
2019 Jun
TiKV 3.0 introduced Titan for larger values and multi-threaded Raftstore and apply processing. Capacity planning increasingly included per-store concurrency as well as total disk space.
2019 Aug
MongoDB 4.2 extended multi-document transactions to sharded clusters. Cross-shard transactional work brought additional coordination and performance cost.
2019 Sep 17
YugabyteDB 2.0 declared its PostgreSQL-compatible distributed SQL API production-ready, adding another open-source path to distributed relational transactions.
2019 Nov
Parallel Commits stages a transaction so recovery can determine its outcome without a separate sequential completion step. The design targets lower cross-range commit latency with a recovery rule.
2019 Nov
SQL Server 2019 continued support for Windows and Linux deployments. Teams planning upgrades needed to consider the product's supported-version lifecycle alongside feature requirements.
2019 Nov
Vitess became a graduated CNCF project after years of production use. The milestone reflected the operational maturity of a reusable sharding layer outside its original YouTube deployment.
46 milestones
2020
NIST published a practice guide for recovering data integrity after ransomware and other destructive events. Recovery procedures increasingly had to account for compromised data and protected backups.
2020 Jan
TimescaleDB documented continuous aggregates with retention and downsampling. The practice made resolution tiers an explicit database policy.
2020 Feb
Neo4j 4.0 introduced multi-database capabilities, finer-grained security controls, and horizontal scaling features. These additions broadened the operational concerns beyond a single graph and query workload.
2020 Apr
Redis 6.0 added access control lists and TLS support. Authentication and command or key permissions became first-class server concerns.
2020 Apr
The 4.0 release candidate added load-based Region splitting. Region boundaries became an active response to traffic shape, not only stored data size.
2020 Jul
MongoDB 4.4 entered the stable release schedule. Its February 2024 end of life reinforces the need to keep deployments on supported release lines.
2020 Sep
The initial Ransomware Guide made offline backups and recovery preparation a prominent part of ransomware response guidance. It placed backup availability and restoration within an adversarial failure model.
2020 Sep 30
Timestream added a purpose-built time-series database. Workloads organized around measurements and time could use a service with time-oriented storage and query behavior.
2021 Mar 16
Prisma made its schema-driven SQL migration workflow available for production use, with separate development and deployment commands.
2021 Jul
Apache Cassandra 4.0 released after an extended validation effort focused on data correctness and production readiness. The release raised the importance of replay, upgrade, performance, and fault-injection testing in the project's practice.
2021 Jul
Cassandra 4.0 reached general availability after an extended testing effort focused on upgrades and operations.
2021 Aug 19
MemoryDB added a durable in-memory database service. AWS users could distinguish a cache from an in-memory primary data store when designing low-latency applications.
2021 Nov
SQLite 3.37.0 adds the STRICT table modifier, enforcing a restricted set of declared types and rejecting values that cannot be converted without loss. Strict typing is a per-table choice, not a database-wide mode, preserving SQLite's dynamic-typing default for existing schemas.
2021 Nov
TiKV 5.3.0 added disk-space protection improvements and flow-control work. Storage headroom became a direct availability and stability signal during production operation.
2021 Nov 23
The deployment combined one primary with two readable standby instances across three zones, making failover targets and read capacity part of one managed topology.
2021 Dec
Neo4j 4.4 was released as the long-term-support version of the 4.x family. Support planning became an explicit version-selection concern for operators.
2022
The project froze the 4.1 release branch in May 2022 for bug fixing before general availability. This formalized a staged release process after the 4.0 validation work.
2022
NIST examined file-system recovery edge cases, including overwritten blocks and TRIM behavior. The guidance sharpened the limits of deleted-data recovery on modern storage.
2022 Mar 31
PCI Security Standards Council published version 4.0 with logging and monitoring retained as a core requirement area. The revision continued the operational focus on defining, protecting, reviewing, and responding to security events affecting account data environments.
2022 Apr
Redis 7.0 shipped with Redis Functions (replacing EVAL scripting), ACL v2, client-side caching, and multi-part AOF persistence — a maturity milestone that narrowed the gap between Redis-as-cache and Redis-as-database.
2022 Apr
Redis 7.0 introduced Redis Functions, which are persisted and replicated server-side programming artifacts. It reduced the need for an application to load its Lua logic at runtime.
2022 Apr
The 6.0 release line continued TiKV's versioned storage-engine evolution alongside TiDB. Operators tracked storage behavior as part of a coordinated distributed SQL stack rather than as an isolated local engine.
2022 Sep 5
Atlas paired versioned migration authoring with ordered execution, a revision table, directory integrity hashes, and baselining.
2022 Oct
Neo4j identifies 5.1 as the first generally available release in the 5.x family. The version line became the successor to the supported 4.x family for compatible drivers and operational planning.
2022 Oct 13
A view could opt into checking base-relation access with the caller's privileges instead of always using the view owner's privileges.
2022 Nov
SQL Server 2022 expanded the platform's choices across languages, data types, on-premises and cloud environments, and operating systems. The release reinforced the course's distinction between SQL Server and its managed Azure relatives.
2022 Dec
Google made AlloyDB for PostgreSQL generally available. The service positioned PostgreSQL compatibility with managed scale-out compute and storage for modernization work.
2023
ISO/IEC 9075-1:2023 published the sixth framework edition and references SQL property graph queries as part of the standard family. SQL continues to grow through coordinated parts rather than one vendor's dialect alone.
2023 Mar
The 7.0 line continued the coordinated TiDB, TiKV, and PD release cadence. Upgrade planning therefore remained a cluster-level activity across SQL, placement, and storage services.
2023 Apr
InfluxData announced InfluxDB 3.0 as a rebuilt time-series storage engine. The release connected these workloads to Arrow, Parquet, and SQL support.
2023 Jul 18
MySQL adopted separate Innovation and Long-Term Support tracks beginning with the 8.1 Innovation release. Version selection became an explicit balance between faster feature delivery and longer stability.
2023 Aug
Aurora added a managed operation for unplanned global failover and renamed the planned operation Global Database Switchover. Operators still had to prepare matching configuration, monitoring, dependencies, and capacity in the target Region.
2023 Sep
CISA's updated guide retained offline encrypted backups and regular recovery tests as core recommendations. It also emphasized restoring prioritized critical services from clean recovery material.
2023 Sep 14
PostgreSQL 16 was released on September 14, 2023. It remains part of the documented sequence that frames supported-version and upgrade decisions.
2023 Sep 14
Membership grants gained independent inheritance and role-assumption controls, plus stronger grantor and dependency tracking.
2023 Oct
MongoDB published guidance on large SQL migrations that centers schema design on relationships and data access patterns. It shows that flexible document structures still require workload analysis during migration.
2024
Oracle Database 23ai became available in Oracle Cloud Infrastructure database services, extending the product line's AI capabilities.
2024 Mar
After Redis Ltd. changed the license to dual RSALv2/SSPL, the Linux Foundation launched Valkey as a BSD-licensed fork backed by AWS, Google Cloud, Oracle, and Ericsson — a reminder that the key-value category's open-source identity can survive a single vendor's licensing decision.
2024 Apr 30
MySQL 8.4 started the first LTS series under the new release model. Operators gained a named long-support track distinct from Innovation releases.
2024 Sep
Cassandra 5.0 added Storage Attached Indexes and marked the 3.x series end of life.
2024 Sep
Apache Cassandra 5.0 became generally available with storage-attached indexes, trie-based storage components, unified compaction, and vector capabilities. It also announced end of life for the 3.x series.
2024 Nov
Prometheus 3.0 arrived after seven years of 2.x development. It retained compatibility as a central concern while removing deprecated feature flags.
2024 Dec
The 8.5 GA line marked a later documented TiKV major release generation. It reinforces that operational procedures must be checked against the matching release documentation rather than assumed from older cluster behavior.
2025
NIST updated media-sanitization guidance. It maintained the distinction between making data unrecoverable and attempting recovery after ordinary loss.
2025 May
SQLite 3.50.0 ships as the 25th anniversary release. The version numbering sequence reaches 3.50 after 25 years of development, with 372 releases and the engine embedded in billions of devices.
2025 May
Redis 8 combined capabilities previously delivered through Redis Stack into Redis Open Source and added further data structures. The distribution changed how practitioners select features and upgrades.