Standard

Apache Avro

A row-based data serialization format with rich schema definition and built-in schema evolution support. Schemas are stored with the data.

4 connections 3 resources

Summary

What it is

A row-based data serialization format with rich schema definition and built-in schema evolution support. Schemas are stored with the data.

Where it fits

Avro is the ingestion format of the S3 ecosystem. Data flowing from Kafka, operational databases, and streaming systems into S3 often arrives in Avro — because Avro's schema-with-data approach handles the frequent schema changes typical of event streams.

Misconceptions / Traps
  • Avro is a row-oriented format. It is efficient for writing and ingestion but inefficient for analytical queries compared to Parquet. Convert to Parquet after landing in S3.
  • Avro's schema evolution rules (backward/forward compatibility) are powerful but strict. Breaking changes silently corrupt data if compatibility modes are misconfigured.
Key Connections
  • used_by Apache Spark — a supported input/output format
  • solves Schema Evolution — schema-with-data approach supports evolution
  • scoped_to S3, Table Formats

Definition

What it is

A row-based data serialization format specification with rich schema definition and built-in schema evolution support. Schemas are stored with the data, making files self-describing.

Why it exists

Data arriving into S3 often comes from streaming systems (Kafka) and operational databases where the schema changes frequently. Avro's schema-with-data approach and backward/forward compatibility rules make it ideal for ingestion layers where schema stability cannot be guaranteed.

Primary use cases

Streaming data ingestion into S3 (Kafka → S3), schema-evolving event logs, interchange format between systems writing to object storage.

Recent developments

Latest signals

Source mix note: Avro's recent corpus is dominated by integration documentation rather than primary engineering posts on the format itself.

  • Schema-registry ecosystem stable across vendors. Per Aiven's Avro Java-class generation docs, the Confluent dependencies version 8.0.0 line remains the reference toolchain for Avro + Java workloads. Per Debezium's Avro serialization reference, Debezium supports both Apicurio and Confluent Schema Registry as backends. Per Evoila's schema-driven messaging guide, the schema-registry landscape now includes Confluent, Apicurio, AWS Glue, Azure, and Karapace as the main options — vendor-neutrality is finally a meaningful procurement axis where it was Confluent-only a few years ago.
  • Latest release: Avro 1.12.1, with 1.11.5 as the maintenance line (October 2025). Both are current across the C#, Java, JavaScript, Perl, Python 3, and Ruby SDKs; documentation remains actively maintained (a new SchemaParser landed in the May 2026 docs refresh). Per Apache Avro downloads and Apache Avro documentation.
  • CVE-2025-33042 — code-injection flaw in the Avro Java SDK. An improper-control-of-code-generation vulnerability affects all versions through 1.11.4 and 1.12.0; the fix shipped in 1.12.1 and 1.11.5, making the 1.12.1 upgrade a security matter rather than routine maintenance for Java consumers deserializing untrusted Avro data. Per CVE-2025-33042 (NVD).

Connections 4

Outbound 4
scoped_to2
S3Table Formats
used_by1
Apache Spark
solves1
Schema Evolution

Resources 3

SpecHigh
avro.apache.org/docs/current/specification/

The authoritative Apache Avro specification defining the schema language (JSON-based), binary encoding, container file format, schema resolution rules, and RPC protocol.

GitHubHigh
github.com/apache/avro

Canonical monorepo containing Avro implementations in Java, Python, C, C++, C#, Ruby, and more, along with the specification source.

DocsHigh
avro.apache.org/

Official Apache Avro project homepage and entry point to language-specific getting-started guides, API docs, and community resources.