Skip to main content

18 posts tagged with "ed-fi-api"

View All Tags

📢 Ed-Fi API v8.1: Now Available

· 4 min read
Vinaya Mayya
Senior Technical Program Manager - API

The Ed-Fi Alliance is excited to announce the release of Ed-Fi API v8.1 and MetaEd v4.9. Ed-Fi API v8.1 builds on v8.0 and restores key capabilities that platform hosts relied on in the Ed-Fi ODS/API, along with new options for performance, data integration, and extensibility.

Deployments running Ed-Fi API v8.0 should upgrade to v8.1 and expect to re-provision their databases. See Supported Versions for the support status of each release.

Have questions about the transition from ODS/API to Ed-Fi API v8? See the Ed-Fi ODS/API and Ed-Fi API v8 FAQ for answers on the roadmap, timelines, and what to expect.

📢 Ed-Fi Admin App 4.1 and Admin API 2.4 Released

· 13 min read
Joseph Campos
Joseph Campos
Software Engineer
David Jiménez
David Jiménez
Software Engineer

The Ed-Fi Alliance is pleased to announce the release of Ed-Fi Admin App 4.1 and Ed-Fi ODS Admin API 2.4, available on GitHub as of November 4, 2026. These releases are designed to work together. Admin API 2.4 adds new ways to manage API credentials, education organizations, and data store (ODS database) instances. It also adds a new v3 mode aligned with the Ed-Fi Management API specification used by Ed-Fi API v8. Admin App 4.1 brings those capabilities to administrators in the user interface.

Ed-Fi Technology Roadmap Update: Fall 2026

· 10 min read
Stephen A. Fuqua
Director, Software Engineering

As we head into another exciting Ed-Fi Summit, the Ed-Fi Alliance has been solidifying its product roadmap and release schedule for 2027.

The schedule is relatively stable: we will continue with the pattern of 1-2 annual releases of each product, spaced out through the year. The product portfolio continues to evolve, including the capabilities served by each product. And the now-completed budget cycle helps us determine what / how much we can actually afford to build.

This update lays out what the Ed-Fi Alliance product team plans to deliver over the next several quarters, what we are deliberately keeping stable, and where the dates are still soft.

tip

Ed-Fi API v8.1 will be released TODAY, with full feature parity with ODS/API 7.3. Keep an eye out for a blog post with more detail, coming soon.

📢 Ed-Fi API Publisher v1.4: Now Available

· 5 min read
Steven Arnold
Manager, Technical Programs

The Ed-Fi Alliance is pleased to announce the release of Ed-Fi API Publisher v1.4. This release adds support for Ed-Fi API v8, reads large sources faster with cursor paging, lets a failed run resume where it stopped, and reports through its exit code whether a run lost documents. It also moves the API Publisher to .NET 10.

Introducing the Ed-Fi API v8 Pilot Test Kit

· 7 min read
Stephen A. Fuqua
Director, Software Engineering

Ed-Fi API v8 has been through a great deal of internal testing: unit and integration tests, end-to-end suites, and the performance comparison against the ODS/API. All of that tells us the platform behaves the way we expect. It does not tell us whether it behaves the way your integration expects. The only way to learn that is to point real client integrations — built by the organizations that will depend on the platform in production — at a running Ed-Fi API v8 instance and see what happens.

That is the purpose of the new Ed-Fi API v8 Pilot Test Kit: a self-contained Docker Compose environment, plus a structured pilot program, for exercising Ed-Fi API v8 with production-grade client integrations before broader market adoption.

(† indicates "coming soon")

Ed‑Fi API 8 Performance: How It Compares to the ODS API

· 13 min read
Vinaya Mayya
Senior Technical Program Manager - API
note

This post reflects the upcoming Ed‑Fi API 8.1 compared against the ODS API v7.3.2.

Overview​

Since the move to a relational backend, the most common question from the community has been simple: how does it perform against the ODS API? We ran a shared test suite against both APIs, on both PostgreSQL and SQL Server, using the same dataset and request mix.

The short version: on PostgreSQL, Ed‑Fi API 8.1 comes out ahead on every workload we tested. On SQL Server, DeepPaging and FilteredRead are close to a tie, and Volume (writes) is behind. The reason is narrow and well understood: the change-version stamp triggers, the database triggers Ed‑Fi API 8.1 uses to keep each record's _etag, last-modified timestamp, and change-tracking version current on every write. We can point to exactly how much they cost and the work already underway to reduce it.

What This Means for Implementers​

  • PostgreSQL: Ed‑Fi API 8.1 wins on writes, paging, and filtered reads against ODS API v7.3.2, on the same hardware and dataset.
  • Where the win comes from: mostly a database CPU advantage on reads. The write path is faster too, but that doesn't mean it's cheaper to run across the board (more on that below).
  • SQL Server: near ties on paging and filtered reads; behind on writes, traced to the change-version stamp triggers, a mechanism we've measured precisely and already scoped a fix for (see below).
  • Read this as a snapshot, not a guarantee for your deployment. See the caveats in the "How We Tested" section below.

📢 Ed-Fi API v8.0: Now Available

· 3 min read
Vinaya Mayya
Senior Technical Program Manager - API

The Ed-Fi Alliance is excited to announce the release of Ed-Fi API v8.0 and MetaEd v4.8. Ed-Fi API v8.0 represents the next-generation evolution of the Ed-Fi ODS/API platform, delivering a modernized architecture while maintaining compatibility with existing Ed-Fi API integrations. Version 8 is designed as the long-term replacement for the legacy ODS/API platform.

Have questions about the transition from ODS/API to Ed-Fi API v8? See the Ed-Fi ODS/API and Ed-Fi API v8 FAQ for answers on the roadmap, timelines, and what to expect.

Ed‑Fi Data Management Service: Moving to a Relational Backend

· 20 min read
Vinaya Mayya
Senior Technical Program Manager - API
note

Ed-Fi API v8 is the production release of the Ed-Fi Data Management Service (DMS) described in this post.

Updated June 17, 2026

This post has been updated to reflect the latest implementation. The most significant change since its original publication is that change tracking is now included.

Overview​

The Ed‑Fi Data Management Service (DMS) is evolving toward a relational backend, shaped by community feedback and real‑world implementation experience. Building on the proven Ed‑Fi ODS/API foundation, DMS modernizes the storage layer to address long‑standing operational challenges—such as wide composite keys and complex joins—through targeted structural changes.

By prioritizing a relational backend, DMS preserves the core strengths of the ODS: predictable schemas, strong referential integrity, and compatibility with relational tooling. The result is a service that feels familiar to teams with ODS experience and lowers the cognitive and migration cost of adoption.

What This Means for Implementers​

If you work directly with the ODS database today, DMS's data store will feel familiar, but with important structural differences:

  • You still work with the same Ed‑Fi entities and natural keys
  • Joins are simpler and narrower due to surrogate keys
  • Person identity is clearer and no longer mediated by ODS-only integers
  • Optional document caching can accelerate API reads

The sections below explain why these changes exist and how they affect database design and operations.

This post is written for database administrators, backend developers, data engineers, and solution architects who work with the Ed‑Fi ODS/API at the database level and are evaluating or planning a transition to DMS. Familiarity with the ODS schema and relational database concepts is assumed.