1956 Sep
IBM 350 RAMAC disk file introduced
The RAMAC introduced random-access disk storage for large computer data volumes. Data processing could move beyond sequential punched cards and magnetic tape for selected workloads.
Data and AI
How the field of a Data Engineer got here: the sourced milestones from every published course of this career, on one axis.
1956 to 2025
260 milestones across 28 courses
The axis stretches toward recent years, where most milestones fall. Bars count milestones per year; dots are single milestones.
13 milestones
1956 Sep
The RAMAC introduced random-access disk storage for large computer data volumes. Data processing could move beyond sequential punched cards and magnetic tape for selected workloads.
1964 Apr
System/360 established a compatible computer family across a broad performance range. Organizations could scale data-processing workloads without moving to an unrelated software architecture.
1968
IBM released IMS for System/360 mainframes. It made database management a distinct platform concern for large operational data.
1970
Edgar F. Codd proposed organizing shared data as relations and separating logical structure from physical storage concerns. The work made declarative relationships and constraints central design ideas.
1970 Jan 1
The IANA time-zone database uses 1970-01-01 00:00:00 UTC as its main scope boundary for locations whose clocks agree. Software later adopted this instant as the POSIX epoch for many timestamp representations.
1970 Jun
Codd described relations and a data sublanguage for large shared data banks. The model separated a user's data view from internal data representation, which became central to later analytical processing.
1971
The Database Task Group documented the network database approach, which made record and set relationships explicit in navigational designs. It became an important contrast for later relational modeling.
1976
Peter Chen published the entity-relationship model as a way to represent entities and their relationships at a conceptual level. ER notation gave modeling a domain-facing design language before physical implementation.
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.
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
SQL became a published standard for relational database language. Modeling decisions about tables, keys, and constraints could increasingly be expressed across vendor implementations.
1987
ISO adopted SQL as ISO/IEC 9075. The paired ANSI and ISO work made SQL an international database-language standard.
1988
ISO 8601 established an international date-and-time representation standard. Its year-month-day ordering became the basis for unambiguous machine-readable dates.
7 milestones
1990
Codd's later book brought relational concepts and their interpretation together for database management practice. It reinforced the distinction between the model's meaning and a particular storage implementation.
1991 Feb
Python's first public release established the language that later became the host environment for numerical and tabular libraries.
1992
Bill Inmon's book established a named body of warehouse architecture and historical decision-support practice.
1992
ANSI and ISO published the revision commonly called SQL-92. It became a long-lived baseline for the portable syntax developers still recognize.
1996
Ralph Kimball's toolkit put fact tables, dimensions, and star schemas at the center of a practical modeling approach.
1997
Ralph Kimball contrasted entity-relationship models for transaction capture with dimensional models for end-user analysis. Facts, dimensions, and grain became a practical vocabulary for analytical design.
1999
SQL:1999 added features including recursive queries and standardized procedural extensions. It widened SQL beyond basic table queries while retaining the relational core.
21 milestones
2000
Dan Linstedt released Data Vault as another approach to historical, auditable integration from changing source systems.
2002 Jul
RFC 3339 specified a constrained Internet profile of ISO 8601 using UTC or numeric offsets. It gave protocols a common syntax for representing an instant.
2003
Google documented a distributed file system designed for large data-intensive applications. The paper made storage behavior a first-class concern in large-scale data processing designs.
2003
Matplotlib's original 2003-2008 project identity marks the emergence of a Python plotting layer for array-based analysis.
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.
2004
MapReduce described a programming model for processing large data sets on clusters. The runtime handled input partitioning, scheduling, failures, and inter-machine communication.
2004
Google described a programming model and implementation for processing large datasets on clusters. It separated map and reduce work into a reusable distributed processing pattern.
2005
NumPy combined earlier Numeric and numarray work into the array library that provides the vectorized numerical base used by pandas.
2006
Google described a distributed storage system for structured data. The design connected large-scale storage with tables, schemas, and application-facing access patterns.
2006
Bigtable described a distributed system for structured data organized around a sparse, multidimensional sorted map. It showed how large-scale storage designs could use a data model unlike conventional relational tables.
2006 Mar 14
Amazon S3 made web-scale object storage available through an API. Object storage later became a common durable layer beneath cloud data lakes.
2006 Apr
Hadoop made its first release after the Nutch MapReduce and distributed-file-system code became a separate project. It provided an open-source path to cluster batch processing.
2007
Dynamo described a highly available key-value store built around partitioning and replication. Its design highlighted how access patterns and failure behavior shape data structure choices in distributed systems.
2008
Development started at AQR Capital Management, introducing the project that made labeled DataFrames central to Python data work.
2008 Jan
Apache created the Hadoop Project Management Committee when Hadoop moved out of Lucene. Hadoop became an independently governed open-source platform for distributed storage and processing.
2008 Jan
Apache Hadoop moved from Lucene to become an Apache top-level project. Its distributed storage and batch-processing ecosystem shaped early large-scale data-lake practice.
2009
Alexey Milovidov and team begin an experimental project to generate analytical reports in real time from non-aggregated data, initially as a filter and aggregation operator for web-scale log data.
2009
Opening pandas development made its DataFrame and I/O workflow available to the wider Python analysis community.
2009
Spark started as a research project at UC Berkeley AMPLab. It introduced a new general processing engine alongside the Hadoop-era ecosystem.
2009
Spark begins as a UC Berkeley AMPLab research project. Its initial direction is distributed data processing with a programming model that can reuse work.
2009 Sep
RFC 5545 standardized iCalendar objects, including components that carry time-zone definitions for calendar data. Calendar interchange therefore had an explicit mechanism for local-time rules rather than only fixed offsets.
109 milestones
2010
Spark moved from the UC Berkeley AMPLab research project to an open-source project. It became another distributed execution engine for data transformations beyond the original MapReduce stack.
2010
Google's Dremel paper described a distributed system for interactive analysis of nested data, influencing later large-scale SQL services.
2010
The Dremel paper described interactive analysis of web-scale datasets through a columnar, multi-level execution tree, publishing the architecture that BigQuery's query engine follows.
2010
The project is open sourced in early 2010. Practitioners can begin using and contributing to the engine outside its research setting.
2010 May
Google announced BigQuery at Google I/O in May 2010 as an external surface of its internal Dremel analysis engine, open first to a limited set of early adopters.
2011
BigQuery made a serverless cloud warehouse available, moving capacity management away from the team submitting analytical SQL.
2011
SQL:2011 added temporal database features. The standard gained a common way to express time-aware data and queries.
2011
Storm made distributed, tuple-at-a-time stream processing broadly available as an open-source system. Its keyed topologies established an early operational model for continuously updated computations.
2011 Jul
Kafka entered incubation as a distributed publish and subscribe project. Apache stewardship established the open project that later became a common event-log implementation.
2011 Nov
After a year in limited beta, BigQuery went to market at the Google Atmosphere conference with a REST API, Google Cloud Storage integration, and a query UI.
2011 Nov
The IANA release archive records 2011 time-zone-data releases. Distributing updated rule data became an operational concern for systems that schedule future civil times.
2012
After three years of development ClickHouse launches in production to power Yandex.Metrica, the second-largest web analytics platform, whose reports it serves from non-aggregated data.
2012
Engineers began Presto to support low-latency interactive analytics over a large Hadoop warehouse. The project established the distributed SQL model inherited by Trino.
2012 Jun
pandas 0.8 adopted NumPy datetime64 for time-series representation, improving joins, memory use, and serialization around dated data.
2012 Oct
Kafka graduated from the Apache Incubator. The project then continued as an Apache top-level project.
2013
Spark moved to the Apache Software Foundation after its early open-source development. This placed the processing engine in the same open-source governance ecosystem as many data infrastructure projects.
2013
Spark moves to the Apache Software Foundation. Development becomes part of an Apache community process.
2013 Feb
Redshift made a managed, petabyte-scale AWS warehouse broadly available for SQL analysis through existing BI tools.
2013 Apr
PROV-O standardized a vocabulary for representing provenance. It gave governance implementations a common model for entities, activities, and agents behind data.
2013 Sep
Release notes added streaming inserts and time-based table decorators, letting rows enter BigQuery continuously instead of through load jobs alone.
2013 Nov
Facebook announced the open-source release of Presto. The project could then be adopted and extended outside its original environment.
2013 Dec
Kafka 0.8.0 was released in December 2013. The 0.8 line established an early operational era whose documentation covers replicated brokers and partitions.
2013 Dec
Kafka 0.8.0 shipped the replication work that made broker failure a durability and availability design concern rather than a single-broker outage.
2014
The first Data Catalog Vocabulary recommendation established a shared vocabulary for dataset and data-service metadata. Catalog interoperability became a standards concern rather than a local schema choice.
2014
Jupyter grew from IPython to support interactive data science and scientific computing across programming languages.
2014
Spark 1.0 introduces Spark SQL and a common spark-submit workflow. Structured-data processing and deployment become first-class parts of the release line.
2014 Mar
The 0.8.1 release continued the replicated-log generation and provided a stable base for production adoption of partition leaders and in-sync replicas.
2014 Mar
BigQuery changed its pricing model, lowering rates and adding reserved capacity pricing, the first step toward the capacity model that later editions formalize.
2014 May
Apache training material records Spark 1.0 in May 2014. A production-ready Spark release broadened the practical choice of engines for batch and stream-oriented workloads.
2014 Aug
Flink moved from the Stratosphere name into Apache incubation. This established a distributed data-processing engine that would become a major stateful-streaming runtime.
2014 Aug
The project published its first incubating release. Stream processing began its path as an Apache community project with downloadable runtime artifacts.
2014 Aug
This was the first Apache Incubator release under the Flink name. The project later centered event time, state, and recovery as core stream-processing concepts.
2014 Sep
Storm graduated from the Apache Incubator, placing distributed real-time computation under Apache project governance. Stream processing became a maintained part of the wider data platform ecosystem.
2014 Oct
Airflow began as an open-source project for defining and scheduling directed acyclic graphs of tasks. It made orchestration a separately visible concern around data-processing work.
2014 Oct
Snowflake documented a cloud-built warehouse architecture with independently sized virtual warehouses for different workloads.
2014 Dec
Flink graduated from the Apache Incubator. The project then continued toward a stable runtime and API for production use.
2014 Dec
The Apache board approved Flink's graduation. The project moved from incubation to a top-level Apache project.
2015
Spark 1.4 expands the DataFrame API and packages SparkR. More structured interfaces become available across language ecosystems.
2015
The timely dataflow model associated communication events with virtual time and formalized progress relationships. It supplied a foundation for stateful incremental systems that reason about when work is complete.
2015 Mar
LinkedIn described tiered clusters and audit counts that checked delivery from producers through downstream consumers. The operational model made end-to-end completeness a concern beyond broker health.
2015 Apr
The 0.9 milestone added a SQL-like Table API alongside other APIs. This established a relational path that later became central to Flink SQL practice.
2015 Aug
The paper formalized choices around event time, windows, watermarks, triggers, and accumulation for unbounded out-of-order data. These abstractions now shape how streaming feature windows are specified.
2015 Nov
Flink 0.10 moved the DataStream API out of beta and added event-time, out-of-order-stream, exactly-once, windowing, state, and high-availability capabilities. These features made operational stream processing a first-class use case.
2015 Nov
Kafka 0.9.0 added Kafka Connect, creating a framework for reusable source and sink integrations instead of application-specific movement for every system.
2016
Pulsar was committed to open source. It expanded the set of distributed messaging and streaming implementations available to practitioners.
2016
ClickHouse is released as an open-source project under the Apache 2.0 license, turning an internal analytics backend into a database other companies can run.
2016
Spark 2.0 starts the 2.x line with Structured Streaming and SQL improvements. Batch and streaming work move toward the same structured programming model.
2016
SQL:2016 incorporated JSON-related features. Relational databases could standardize some work with semi-structured values without abandoning tables, constraints, and joins.
2016
Uber developed Hudi to address inefficient snapshot-and-reload processing and to support incremental updates in its data lake.
2016 Feb
Google and partners moved Cloud Dataflow SDKs and runners into the Apache Beam Incubator. The project centered one programming model across batch and streaming pipelines.
2016 Mar
Airflow entered the Apache Incubator. The project moved from its original creation at Airbnb into Apache's community governance path.
2016 Mar
The 1.0 release marked a stable project milestone and brought Flink to a broader production audience for distributed stream processing.
2016 Mar
Flink 1.0 formally guaranteed compatibility for APIs marked public across the 1.x line. It also added a RocksDB state backend and checkpoint statistics for operating larger state.
2016 Mar
RFC 7808 defined an HTTP service for clients to discover and retrieve time-zone data. The protocol recognized that applications may need current rule data beyond their local installation.
2016 Apr
Regulation EU 2016/679 set a common European framework for personal-data processing. Governance programs needed to connect processing decisions to accountable roles and controls.
2016 May
Kafka 0.10.0.0 introduced Kafka Streams, making a Java client library part of the path for transformations, joins, and aggregations over topic data.
2016 Jun
Beam released a pipeline SDK with runners for Flink, Spark, and Google Cloud Dataflow. It formalized a portable model that can express batch and streaming pipelines across execution environments.
2016 Jun
Beam first released a unified programming model with Flink, Spark, and Google Cloud Dataflow runners. Pipeline logic could be expressed separately from an execution engine.
2016 Jun
Kafka 0.10 introduced an embedded stream-processing library and message timestamps. Application teams could maintain keyed transformations without operating a separate processing cluster.
2016 Jun
An ANSI-compliant Standard SQL dialect entered beta alongside fine-grained IAM roles and native time partitioning, removing the need for manually date-suffixed tables.
2016 Jul
dbt development began in 2016, bringing versioned SQL modeling, testing, and documentation practices into warehouse transformation.
2016 Sep
Pulsar became an Apache Incubator project, moving its development into the Apache community.
2016 Sep
Standard SQL became generally available with INSERT, UPDATE, and DELETE support, and flat-rate pricing offered unlimited querying for a fixed monthly price.
2016 Dec
Apache Beam graduated from incubation in December 2016. The project established a community-governed model for engine-independent pipeline definitions.
2017
Databricks began providing Delta Lake to customers as an ACID table-storage layer over cloud object stores. Its design used table metadata to identify the objects in a table.
2017
Uber released Hudi as open source after developing it for incremental data processing. The project introduced a table-oriented approach to lake data before the lakehouse label became widespread.
2017 Mar
Beam released its Python SDK in version 0.6.0. This expanded access to the same pipeline model beyond Java.
2017 May
Apache Beam published version 2.0.0 as its first stable release. The release signaled API stability for teams building portable batch and streaming pipelines.
2017 May
Beam declared API stability with version 2.0.0. That made the portable model more suitable for long-lived production pipelines.
2017 May
Dmitry Petrov published the first DVC blog post on May 4, 2017. The project began with the goal of bringing Git-linked versioning and reproducibility to data science artifacts.
2017 Jun
Flink 1.3 added Web UI watermark monitoring and completed-job history through the HistoryServer. Practitioners gained direct signals for diagnosing stalled event-time progress and reviewing finished jobs.
2017 Jun
Kafka 0.11 made idempotent and transactional producer modes available, which enabled atomic Kafka output and consumed-offset commits within a defined boundary.
2017 Sep
Yandex publishes the account of Metrica's storage evolution from MyISAM through Metrage and OLAPServer to ClickHouse, the narrative this course uses for the problem the engine exists to solve.
2017 Sep
The project continued its incubating release line before the 2.x platform releases.
2017 Sep
Uber documented a centralized feature store whose canonical features could be consumed online and offline. The design made feature reuse and training-serving consistency visible platform concerns.
2017 Nov
Kafka 1.0.0 included improvements for exactly-once semantics. The release made transactional processing a documented part of the platform's delivery toolkit.
2017 Nov
Kafka 1.0.0 was released in November 2017. The 1.0 release became a long-lived upgrade starting point for clusters whose operators later planned multi-version paths.
2018
Mark Raasveldt and Hannes Mühleisen start DuckDB at Centrum Wiskunde & Informatica in Amsterdam as an embeddable analytical database project.
2018
Nick Schrock began the project that became Dagster. The early work established the software-engineering approach that preceded the stable 1.0 APIs.
2018
The original creators left Facebook and formed an independent community around PrestoSQL. This created the project line that later became Trino.
2018 Apr
The 2.0 line established the major-version release series used by later platform features.
2018 May
The regulation began applying across EU Member States. Organizations needed operational evidence for privacy decisions, not only written policies.
2018 Jul
BigQuery ML let teams create and run machine learning models with SQL statements such as CREATE MODEL and ML.PREDICT, keeping training data inside the warehouse.
2018 Jul
Kafka 2.0.0 was released in July 2018. Operators gained another major-version boundary where compatibility and staged rolling upgrades became explicit maintenance work.
2018 Aug
The release added the connector framework and storage offload capabilities that widened the platform beyond brokered delivery.
2018 Sep
Pulsar graduated as an Apache top-level project. Its governance milestone reflected the growth of a separate streaming ecosystem.
2018 Sep
The paper described the distributed coordinator and worker architecture, connectors, query planning, resource management, and fault-tolerance tradeoffs in production Presto.
2018 Nov 16
The project began incubation at the ASF after originating at Netflix. Public community development of the open table format started under incubator governance.
2018 Dec
Hopsworks introduced an open-source feature-store layer for sharing, documenting, and governing feature data. This moved the pattern beyond internal platforms.
2019
The peer-reviewed demo paper "DuckDB: An Embeddable Analytical Database" documents the design goals behind the early public release.
2019 Jan
Apache Airflow graduated from the Incubator and became a top-level project. The project then operated with its own Apache project governance and release process.
2019 Jan
GO-JEK and Google Cloud announced Feast for defining, storing, discovering, and reusing features across training and production. It established a vendor-neutral integration layer around existing data systems.
2019 Jan
Uber submitted Hudi to the Apache Incubator. The move placed a transactional data-lake project under Apache community governance.
2019 Feb
The February platform release recorded Delta Lake general availability, making reliable table behavior a standard platform capability.
2019 Apr
Databricks announced the Delta Lake open-source project. The table layer became available outside its original managed platform context.
2019 Apr
Databricks released Delta Lake as an open source project, separating the table protocol from a Databricks-only product name.
2019 Apr
Flink 1.8 remained API-compatible for public APIs in the 1.x series. Compatibility became a practical consideration for maintaining long-running applications through upgrades.
2019 Apr
Managed MLflow reached general availability in the workspace, extending the platform to experiment tracking.
2019 May
BigQuery ML exited beta, making SQL-native model creation and prediction a supported part of warehouse practice.
2019 May 20
Zhamak Dehghani's article on moving beyond a monolithic data lake proposed domain-owned data products, each defining its integrity as a set of service level objectives and publishing schemas. It framed data as a product with explicit promises to consumers.
2019 Jun
The first preview release and conference announcement present an analytical SQL engine that runs as a binary or inside host processes such as Python and R.
2019 Jun
The United States issued a government-wide framework for managing federal data. It placed ethical governance, accountability, and implementation practices in a long-term strategy.
2019 Jun 23
The Iceberg specification was migrated to git and the ASF site. The format contract became an openly versioned community artifact rather than a company-only document.
2019 Aug
A Trino engineering change used dictionary blocks for UNNEST output. It reduced CPU and allocation work for the tested operator workload.
2019 Sep
The Federal Data Strategy required inclusive and empowered governance bodies. Authority, chartering, and senior participation became concrete operating requirements.
2019 Sep
The 2.5 release continued the stable Apache Pulsar release line after incubation.
2019 Oct
RFC 8536 documented the Time Zone Information Format used to distribute compiled time-zone data. It made the boundary between IANA source rules and runtime-consumable zone files explicit.
2019 Oct 25
The project shipped 0.7.0-incubating with source and convenience binaries. Downstream engines could depend on a numbered Apache release artifact.
2019 Nov
Microsoft introduced Azure Synapse as the next evolution of Azure SQL Data Warehouse, combining warehouse and broader analytics workloads.
110 milestones
2020 Jan
NIST released a privacy-risk framework for enterprise risk management. It connected data-processing decisions with privacy risk.
2020 Jan
pandas 1.0 formalized a deprecation and major-release policy, making API evolution more legible for long-lived analysis code.
2020 Feb
DCAT 2 revised the catalog vocabulary after implementation experience and new use cases. It extended the standards path for metadata exchange.
2020 Mar
The high-throughput, parallelizable read API over BigQuery storage reached GA, letting engines such as Spark and TensorFlow read warehouse data directly.
2020 Mar
The 20.3 LTS release continues the versioned release cadence that ClickHouse still follows, anchoring the era when the open-source project's adoption broadened beyond Yandex.
2020 May
The 1.0 prerelease consolidated pipeline stages into one metadata file and added run-cache and remote-operation improvements. These changes prepared a stable project structure for automated data and model workflows.
2020 May
A rewritten streaming path delivered seconds-level availability of streamed rows and removed the warm-up delay of the original streaming implementation.
2020 May
PEP 615 introduced the zoneinfo module for IANA time-zone support in Python. It brought named-zone handling and transition behavior into a standard runtime API.
2020 May 20
The project left the Incubator. Governance and releases continued as an Apache top-level project for the table format.
2020 Jun
DVC 1.0 formalized text metadata pointing to artifact content in remote storage and improved pull, push, remote status, and garbage-collection behavior. The release marked the versioning workflow as a mature foundation for MLOps.
2020 Jun
Spark 3.0 adds adaptive query execution and dynamic partition pruning. Runtime statistics can now influence selected query-execution strategies.
2020 Jun 4
The Apache Software Foundation announced Hudi as a top-level project. Its maturation reflected sustained adoption of transactional capabilities over data-lake storage.
2020 Jul
Michel Tricot and John Lafleur began building Airbyte as an open-source data integration project. The goal was to replace hand-written per-source extraction code with reusable connectors.
2020 Jul
Omni extended BigQuery queries to data in Amazon S3 and Azure Blob Storage by running the engine in the other cloud, with no cross-cloud data movement.
2020 Aug
The 2.6 release continued the platform’s regular feature-release cadence.
2020 Sep
Airbyte published version 0.1 with three source connectors and two destination connectors. It established the connector-plus-platform split the product still uses.
2020 Oct
The project documented unaligned checkpoints as a response to checkpoint alignment delays under backpressure. Checkpoint behavior became a more explicit latency and recovery design choice.
2020 Nov
Databricks introduced a SQL environment for ad hoc queries and dashboards on lakehouse data.
2020 Dec
Airflow 2.0 introduced the TaskFlow API, scheduler high-availability work, and separately released provider packages. Dag authors could use decorated Python functions while deployments selected providers for external systems independently of core.
2020 Dec
The release continued Flink's work toward unified DataStream and Table APIs. Practitioners could use a closer programming surface for bounded and unbounded workloads.
2020 Dec
The PrestoSQL project adopted the Trino name. The rename retained the project and community while separating its identity from Presto.
2021
An independent foundation takes custody of most project intellectual property so DuckDB remains MIT-licensed with long-term continuity separate from any single company.
2021 Jan
The CIDR paper defined a lakehouse as data-lake files plus a metadata, caching, and indexing layer. It connected transaction and versioning mechanisms with SQL, data-science, and machine-learning workloads.
2021 Jan 3
Release 351 was published as an early Trino release. Its release notes record the continuing release stream after the rename.
2021 Mar
DVC 2.0 introduced Git-reference-based experiments, model checkpoint versioning, pipeline templating, and DVCLive metrics logging. Artifact versions could now remain connected to rapid experiment states without ordinary branches for every run.
2021 Mar
Airbyte raised a 5.2 million dollar seed round led by Accel. The funding supported building the core team and connector catalog.
2021 Mar 12
Shopify's engineering blog described its move to log-based change data capture and named its main drawback: external consumers become tightly coupled to the source's internal data model, so breaking changes spread into every consumer.
2021 Apr
Kafka 2.8.0 introduced early access to replacing ZooKeeper with a self-managed quorum. This began the shift toward operating a controller quorum as part of Kafka itself.
2021 Apr 8
Writing about GoCardless, Andrew Jones proposed that producers emit events designed for consumers, with a strongly defined schema that is documented, versioned, and protected from breaking changes. He called that schema a data contract.
2021 May
Flink 1.13 extended the runtime and Table API ecosystem for streaming applications. It continued the platform's progression after the earlier API-unification work.
2021 May
Databricks introduced Unity Catalog for fine-grained governance of data and artificial intelligence assets across workspaces.
2021 May 25
Airbyte announced a 26 million dollar Series A led by Benchmark. The round funded development toward a hosted service.
2021 Jun
DVC Studio added a web interface for experiment tables, metrics, parameters, and collaboration based on Git and DVC project history. Teams gained a shared view without placing large data or models in Git.
2021 Jun
The release documented further development of Pulsar as a unified messaging and streaming platform.
2021 Jun
Table snapshots offered low-cost, read-only point-in-time copies of tables, turning audit and restore patterns into a built-in feature; they reached GA the same October.
2021 Jul 14
The core engineering team forms DuckDB Labs as a CWI spin-off for full-time development and commercial support around the open-source engine.
2021 Sep
ClickHouse, Inc. incorporates in Delaware with an initial $50M investment from Index Ventures and Benchmark, followed in October by a $250M Series B at a $2B valuation.
2021 Sep
Flink 1.14 supported checkpoints after tasks finish and a final checkpoint for bounded inputs, enabling mixed bounded and unbounded applications to commit sink results correctly.
2021 Sep
Kafka 3.0 advanced the built-in KRaft consensus mechanism intended to replace ZooKeeper, moving metadata management into Kafka's own architecture.
2021 Sep
Kafka 3.0 introduced KRaft metadata and API improvements while the mode was still not recommended for production. Operators began planning for a controller model without ZooKeeper.
2021 Sep
Kafka 3.0.0 added metadata-topic snapshots and other self-managed quorum improvements. KRaft operation became a more concrete path for clusters evaluating their metadata plane.
2021 Oct
Airflow 2.2.0 released as the project continued the 2.x series. The release history records it as the 2021 major release before the later data-aware scheduling work.
2021 Oct
A production report connected uneven task CPU time and JVM compilation behavior to slow queries. It demonstrated why worker-level observations matter alongside SQL plans.
2021 Oct
The stream-based write API with exactly-once delivery semantics reached GA, replacing the legacy streaming path for high-throughput ingestion.
2021 Nov 16
The company behind Dagster announced a 14 million dollar Series A. The funding supported development of the open-source project and its commercial service.
2021 Dec
Databricks SQL reached general availability, placing governed SQL analytics within a lakehouse platform alongside other workloads.
2021 Dec 17
Airbyte closed a 150 million dollar Series B led by Altimeter Capital and Coatue Management, at a reported 1.5 billion dollar valuation.
2022
The company launches the early access program for its managed cloud service, opening the storage-and-compute management layer that ClickHouse Cloud automates today.
2022 Apr
BigLake launched with tables over GCS, S3, and Azure storage, enforcing fine-grained security consistently across BigQuery and open-source engines.
2022 Apr
The 2.10 release extended the established 2.x line before the next major version.
2022 Apr 7
Airbyte launched its hosted Cloud service and acquired Grouparoo, an open-source reverse-ETL company, adding a path to send warehouse data back out to operational tools.
2022 Jun
The extension brought dataset and model management, experiment execution, metrics, and plots into the editor. DVC workflows gained a graphical path that still used project metadata and local artifacts.
2022 Jul 16
Release 0.14.0 introduced a common REST catalog client with change-based commits and metadata APIs for table branches and tags. Catalog interoperability and named refs became first-class project features.
2022 Aug
Unity Catalog became generally available, making its governed namespace and access model a stable platform foundation.
2022 Aug 5
Dagster marked its core abstractions as stable. Assets, ops, graphs, jobs, schedules, and sensors could then be adopted without the pre-1.0 breaking-change expectation.
2022 Aug 9
The managed service became generally available alongside the 1.0 era. Teams could use a hosted control plane instead of operating every deployment component themselves.
2022 Aug 22
Chad Sanderson described production database schemas used by ELT and CDC tools as non-consensual APIs and presented data contracts as API-like agreements between service engineers and data consumers.
2022 Sep
Airflow 2.4.0 released as the project's data-aware release. It made dataset-based scheduling a first-class direction alongside time-based schedules.
2022 Sep
The 0.5 series continues the named-release cadence as the engine moves through wider production adoption ahead of a stability-focused 1.0.
2022 Oct
Kafka 3.3 marked KRaft production ready for new clusters. The guidance still distinguished new deployments from migration of existing ZooKeeper-based clusters.
2022 Oct
Kafka 3.3.1 documented KRaft mode as production ready for new clusters, making controller and broker role design a standard operational concern.
2022 Nov
DuckDB Labs partners with MotherDuck to provide a managed cloud path for shared storage, collaboration, and operations on top of DuckDB.
2022 Nov 3
The 1.0.0 release committed to semantic versioning for the public iceberg-api module. Integrators could treat the Java API as stable across 1.x.
2022 Nov 28
Release 1.1.0 let Spark and related paths read and write named branches and tags. Write-audit-publish style workflows moved from metadata API only into engine-facing operations.
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
Spark 3.4 adds Spark Connect client API coverage in Python. Client applications can interact with a remote Spark service through a decoupled interface.
2023 Feb
Kafka 3.4 added early-access migration from ZooKeeper to KRaft. The feature was intended for testing rather than production use at that point.
2023 Feb
Kafka 3.4 added the migration path from ZooKeeper mode to KRaft mode, turning the architectural transition into an upgrade-planning concern for existing clusters.
2023 Feb
DVC added a workflow that records provider version identifiers for data already protected by cloud object versioning. This created an alternative to the traditional hash-shaped remote layout for supported storage.
2023 Mar
Three compute tiers, Standard, Enterprise, and Enterprise Plus, introduced capacity-based pricing with autoscaling and per-second slot billing, closing flat-rate commitments to new purchases.
2023 Mar
Pulsar entered the 3.x release line, marking a new major-version baseline for users and operators.
2023 Apr
Airflow 2.6.0 released in April 2023. It continued the regular 2.x release cadence before the later 2.10 and 3.0 architectural work.
2023 Apr 27
dbt Core 1.5 introduced model governance features, including access, contracts, and versions. An enforced contract makes dbt check column names and data types before building a model.
2023 May 1
PayPal released its data contract template, used in its data mesh implementation, under the Apache 2.0 license. Version 2.1.1 covered schema, data quality, pricing, stakeholders, roles, and service levels, not only structure.
2023 May 18
Airbyte released the Connector Builder, an in-UI tool for creating API source connectors without a local development environment. It also underpins the low-code declarative connector format.
2023 May 24
The company announced a 33 million dollar Series B. The announcement reported total funding of 48.8 million dollars.
2023 Jun
DVC 3.0 expanded partial dataset modification, cloud-versioned imports, the DVC filesystem API, and transfer performance. The release kept data versioning at the core while broadening command-line, Python, editor, and web access.
2023 Jun
Kafka 3.5.0 marked ZooKeeper as deprecated and described ZooKeeper-to-KRaft migration as early access. Upgrade planning now needed a migration decision, not only a broker rollout.
2023 Jul 27
Version 2.2.0 renamed the template to the Open Data Contract Standard and finalized its fork under the AIDA User Group, turning a company template into a community specification.
2023 Aug 21
The company renamed itself Dagster Labs. The change aligned the company identity with the open-source project and managed product.
2023 Aug 29
Airbyte replaced dbt-based basic normalization with destination-native Typing and Deduping. Streams now map one-to-one to final tables, and a bad value is nulled and logged in _airbyte_meta rather than failing the sync.
2023 Sep 12
The datacontract.com project published version 0.9.0 of its own YAML format for data contracts, following OpenAPI and AsyncAPI conventions.
2023 Oct 4
Iceberg 1.4.0 shipped a large feature set. From 1.4.0 onward, new tables default to format-version 2, making delete-file capable tables the common baseline for fresh deployments.
2023 Oct 11
Dagster Labs introduced a free self-guided learning platform. Dagster Essentials was its first course.
2023 Nov 30
The Bitol project, home of ODCS, became a sandbox project of the Linux Foundation AI & Data Foundation, placing the standard under vendor-neutral governance.
2024
Ecosystem collaboration continues as MotherDuck contributes substantially to the DuckDB Node.js client later in 2024.
2024 Feb 27
Airbyte published PyAirbyte, a Python library that runs connectors locally with a DuckDB cache and no Airbyte server. It made connectors usable directly from scripts and notebooks.
2024 Mar
The maintained 3.0 line continued with a published stable release in 2024.
2024 Apr 17
Dagster Labs presented Dagster+ as the managed product identity. The name now distinguishes the managed offering from the open-source engine used in this course.
2024 May
RFC 9557 extended RFC 3339 timestamps with additional information, including a bracketed IANA time-zone name. It lets a representation carry both an observed offset and the rules intended for local-time interpretation.
2024 Jun
Airbyte announced it would end support for Docker Compose deployments in favor of Kubernetes, with the new abctl tool running a local kind cluster for single-machine installs.
2024 Jun
Databricks introduced Lakeflow as a grouped experience for ingestion, transformation, orchestration, and monitoring of data pipelines.
2024 Jun
NumPy 2.0 marked a major release of the numerical layer beneath many Python analysis workflows.
2024 Jun 3
Version 1.0 emphasizes storage backward compatibility and a more cautious SQL and C API change policy so applications can depend on clearer compatibility expectations.
2024 Jul 25
Release 453 appears in the official release archive. The release cadence shows the project continuing to evolve after the Trino rename.
2024 Aug
Airflow 2.10.0 released in August 2024 with dataset improvements and the Hybrid Executor. The release showed continued investment in data-aware workflows and execution choices in the 2.x line.
2024 Aug
DCAT 3 updated the catalog vocabulary for additional use cases. It remains a current standards reference for interoperable catalog metadata.
2024 Aug
The first ClickHouse research paper appears at VLDB, documenting the MergeTree storage layer, merge-time transformation, pruning techniques, and vectorized query execution; the docs' architecture overview is its web version.
2024 Sep 24
Airbyte marked its platform 1.0 and made Self-Managed Enterprise generally available. The release signaled a stable API and upgrade path for self-hosted users.
2024 Oct 21
ODCS v3 replaced the table-and-column schema with objects and properties, so one format can describe relational, hierarchical, and streaming data, and added the servers and support sections. A technical steering committee from 14 companies backed the release.
2024 Oct 31
Dagster 1.9 marked Declarative Automation as stable. AutomationCondition became the mature asset-state mechanism alongside schedules and sensors.
2024 Nov
Kafka 3.9.0 introduced dynamic KRaft controller membership and was the final major release with ZooKeeper mode. Controller membership became an administrative operation.
2025
ClickHouse announces $350M Series C financing at its inaugural user conference, OpenHouse, in San Francisco, marking the company's second major funding round after incorporation.
2025
Spark 4.0 begins the 4.x line with expanded Spark Connect and SQL capabilities. Client-server usage and structured query features continue to evolve together.
2025 Mar
DuckLabs and MotherDuck ship a browser-based local UI via the ui extension, with an explicit path to connect to MotherDuck when cloud features are needed.
2025 Mar
Kafka 4.0 became the first major release to operate entirely without ZooKeeper and made KRaft the default mode.
2025 Mar
Kafka 4.0.0 became the first major release to operate entirely without ZooKeeper. KRaft mode became the default operational model and upgrade paths needed to account for it.
2025 Apr
Airflow 3.0 introduced the Task Execution Interface and API-server architecture, Dag versioning, scheduler-managed backfills, and data assets. These changes separated task execution more clearly from the metadata-database control plane.
2025 May
DuckLabs introduces DuckLake, keeping lakehouse catalog metadata in a SQL database while storing table data as open Parquet.
2025 Sep
Airflow 3.1.0 added human-in-the-loop workflows, deadline alerts, internationalization, and a React plugin system. It extended the Airflow 3 platform after the 3.0 architecture transition.