It all started during the pandemic in 2020. Disc golf exploded in popularity, but the discs? They vanished from shelves as fast as they arrived. The second-hand market went crazy with sky-high prices, and finding a specific disc felt like searching for a needle in a haystack.

I simply missed having a place where you could see all available discs in one spot – without having to check ten different online stores every day. So I built it myself! 🥏

Today, Discinstock helps disc golfers across Norway compare prices and discover new discs. The goal is simple: make it easier to find what you're looking for, and maybe save a few bucks along the way.

Compare prices – See prices from multiple Norwegian stores in one place. Find the best deal without clicking through the entire internet.

Smart filtering – Search by disc type, brand, flight specs, or price. Find exactly the disc you need for your throw.

Stay updated – Discinstock regularly updates its inventory so you can catch new arrivals and restocks.

As someone who enjoys both disc golf and good technology, I wanted Discinstock to be fast and smooth. Here's what powers it:

How the data is collected

Discinstock uses automated web scrapers (spiders) to collect disc information from online stores. These spiders run in a Kubernetes cluster and send their findings through RabbitMQ into a data pipeline. The pipeline handles storage and enrichment – matching discs across stores, extracting flight numbers, and keeping everything organized.

The tech stack

Frontend:

• Nuxt 4 – A Vue-based framework for modern web apps with server-side rendering
• TypeScript – Type-safe code for fewer bugs and better developer experience
• BeerCSS – A lightweight CSS framework based on Material Design 3
• Pinia – State management for Vue, handling filters and sorting
• Cloudflare Workers – Edge hosting for fast page loads worldwide

Backend:

• Python + FastAPI – The API serving disc data to the frontend
• RabbitMQ – Message queue for coordinating data from multiple spiders
• Kubernetes – Container orchestration for running spiders, API, and data pipelines

Why these choices?

The frontend runs on Cloudflare's edge network for low latency, while the backend lives in Kubernetes for flexibility and scalability. It's a hobby project that grew a bit, so I wanted a setup that's fun to work with and can handle future growth without breaking the bank.