One Source of Truth: The Vision Behind discgolf.buzz

Every great project starts with a problem worth solving. For THE Buzz, that problem was hiding in plain sight — and every disc golf fan had already experienced it dozens of times without ever putting a name to it.

You finish watching a tournament broadcast. You want to know what happened on the lead card on hole 16. You open four different tabs. You check a YouTube channel. You scroll through a subreddit. You search Twitter. You find three different accounts of the same moment, none of them linking to each other, none of them with the full picture. You close your laptop slightly frustrated and slightly less informed than you wanted to be.

That experience — fragmented, scattered, incomplete — was the starting point for everything we built.

The Brainstorm: What Does Disc Golf Actually Need?

The earliest conversations about THE Buzz were not about technology. They were about the community and what it was missing.

Disc golf has grown faster than its infrastructure. In the span of a decade the sport went from a niche hobby to a legitimate professional circuit with elite athletes, significant prize money, and a global fanbase tuning in from dozens of countries. The courses got better. The equipment got better. The athletes got better.

The media ecosystem did not keep pace.

Content existed — good content, even great content — but it lived in isolated pockets. A YouTube channel here. A podcast there. A stats site maintained by a volunteer who might burn out next year. A Facebook group for local news that newcomers could never find. Nothing connected. Nothing aggregated. Nothing served as the authoritative record of what was happening in the sport at any given moment.

The brainstorm kept returning to one idea: disc golf needed a single source of truth.

What a Single Source of Truth Actually Means

In software architecture, a single source of truth is a principle — the idea that every piece of data in a system has one canonical home, and everything else references that home rather than maintaining its own copy.

We borrowed that principle and applied it editorially.

If a tournament happens, the result should live in one place — structured, queryable, and referenced by everything else that talks about it. If a player signs with a new sponsor, that fact should exist in a record that news articles, player profiles, and video metadata all point to. If a course opens in a new city, its data should be entered once and surfaced everywhere it is relevant — not typed into five different posts by five different writers who might each spell the course name slightly differently.

This sounds obvious when you say it out loud. It is surprisingly rare in practice.

Building toward a single source of truth forced us to think about data before we thought about content. Before we wrote a single article, we asked: what is the underlying record this article is about? Before we embedded a single video, we asked: what structured data should exist alongside this video so that other systems can understand what it contains?

That discipline shaped everything about how discgolf.buzz is built.

The Microservices Philosophy

Once we committed to a single source of truth, the architectural path became clearer. We did not want to build a monolith — one massive application that did everything and therefore owned everything and therefore became impossible to change without breaking something else.

We wanted microservices. Small, focused, independently deployable pieces that each did one thing well and communicated through open interfaces.

In practice that means:

The content layer manages editorial content — news, articles, video metadata, player information. It does not care how that content is displayed. It exposes it through an API and lets anything consume it.

The presentation layer takes content from the API and renders it for human readers. It is optimized for performance and search visibility but it does not own the data. If we rebuilt the entire frontend tomorrow, the data would be unaffected.

The import and enrichment layer is a collection of scripts and tools that bring data into the system — scraping, normalizing, enriching with AI-generated metadata, and writing to the content layer through its API. It runs independently and could be replaced or extended without touching anything else.

The video layer indexes disc golf video content from across the internet, normalizes it into a consistent structure, and makes it searchable and filterable. It knows nothing about how videos will be displayed. It just maintains the record.

The group and community layer — currently in development at mydiscgolf.buzz — will give local clubs and disc golf groups their own slice of the platform. Each group gets its own space, its own content, its own data. But all of it is connected to the same underlying infrastructure and the same open API.

Each layer talks to the others through documented interfaces. Each layer can evolve independently. Each layer can be scaled independently if one part of the system grows faster than another.

Why Open API Was Never a Question

When you build on a single source of truth, openness becomes the natural conclusion.

If the data lives in one canonical place and everything references it — why would you hide it? The value is not in hoarding the data. The value is in being the place where the data lives, being the team that maintains its quality, and being the platform that builds the best experiences on top of it.

We made the decision early: the discgolf.buzz API would be public, documented, and free to use. No application process. No API keys for basic access. No terms designed to prevent competitors from building on our data — because a thriving ecosystem of disc golf applications built on our data is better for the sport than a single application we control.

If a developer builds a fantasy disc golf platform on our API and it becomes more popular than discgolf.buzz itself, that is a success. It means we built the right foundation.

Community as Infrastructure

The most important insight from the brainstorming process was not technical. It was social.

A single source of truth only works if the community trusts it. Data quality is not a database problem — it is a community problem. The reason Wikipedia works is not because of its software. It is because of its community of contributors who care enough to maintain it.

We designed discgolf.buzz with that in mind. The platform is not just a place to consume content. It is infrastructure for the disc golf community to build on. Local groups, independent developers, tournament organizers, course managers — all of them should be able to use what we have built and contribute back to the record.

The upcoming club and group platform at mydiscgolf.buzz is the first expression of that vision. Local disc golf groups will be able to claim their own space, manage their own content, and connect their data to the broader ecosystem. A club in Kansas City and a club in Stockholm will both be part of the same record. Their tournaments, their members, their courses — all connected through the same open API that powers discgolf.buzz.

What We Learned from Building It

Building toward a single source of truth is harder than building a traditional website. It requires you to resist the temptation to take shortcuts — to just hardcode that player's name, to just copy that result into a text field instead of creating a proper relationship, to just ship the thing and clean it up later.

Later never comes. The shortcuts compound. The data becomes inconsistent. The single source of truth becomes multiple sources of approximate truth, which is just fragmentation with extra steps.

The discipline of doing it right from the beginning is what makes the system trustworthy over time. And trustworthiness — of data, of coverage, of the platform itself — is the only thing that makes a media destination worth returning to.

Disc golf deserves that. The community has been building something remarkable for decades. THE Buzz is here to be the infrastructure that holds the record of it.

Come Build With Us

The brainstorm never really ends. There is more to build, more data to structure, more community to connect.

If you are a developer, a disc golf organization, a tournament director, or a club manager who sees what we are building and wants to be part of it — reach out. The API is open. The platform is growing. The community is the point.

discgolf.buzz