apache/avro

Apache Avro is a data serialization system.

View on GitHub ↗Jump to charts ↓

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 5 minutes ago
Added to GitGenius on September 21st, 2026
Created on May 21st, 2009
Open Issues & Pull Requests: 255 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 1,778
Total Stargazers: 3,307 (+0)
Total Subscribers: 101 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Apache Avro is a data serialization system that enables efficient encoding and decoding of structured data across multiple programming languages.

Avro solves the problem of serializing complex data structures in a way that is both compact and language-agnostic. It uses a schema-based approach where data is described by a JSON schema that defines the structure, types, and organization of fields. The serialization format is binary, which keeps the encoded data small, and the schema travels with the data or is referenced separately, allowing consumers to understand and deserialize messages even if they were produced by different systems or written in different languages.

Avro is well-suited for big data pipelines, message streaming systems, and any architecture where data moves between services built in different languages. It is particularly valuable in ecosystems like Hadoop and Kafka where interoperability and compact storage matter. The tool supports a wide range of languages including Java, Python, C, C++, C#, Ruby, PHP, and Perl, making it practical for polyglot environments. Choose Avro when you need a standardized format that multiple teams or systems must agree on, or when you are building infrastructure that will outlive individual application versions and needs to handle schema evolution gracefully.

Development activity on the project is steady and distributed across multiple language implementations. Contributions span the core Java implementation and bindings for other languages, indicating ongoing maintenance of the multi-language ecosystem. The project maintains active engagement with schema evolution and compatibility concerns, which are central to its design philosophy. Work continues on performance improvements and bug fixes across the supported language implementations.