3 of 4

Loading

01
Euro Basalt, cover

backend

Euro BasaltEuro Basalt

The backend behind eurobasalt.mn: database design, business logic, the API its Next.js site reads, and integrations with the systems that own the content.

  • 2026 to Now
  • 1 frame
  • Go (Golang)
  • REST API
  • PostgreSQL
  • Next.js
02

Case study

What it changed

  1. The problem

    Euro Basalt (eurobasalt.

    • mn) is a Mongolian basalt-materials company whose public site is a Next.
    • js frontend served entirely from an API.
    • A landing site like that looks like the easy case until the content becomes dynamic and the traffic arrives in bursts, with everything a page needs fetched on every request.
  2. What I built

    I built the backend: the data model behind the pages, the business logic, the endpoints the frontend consumes, and the integrations that pull content and data in from the systems that own it.

    • I designed the database myself rather than only writing queries against someone else's schema, and put most of the effort into performance and data processing, trimming the slow paths.
  3. What it changed

    Everything a page needs is cheap enough to fetch on every request, even with dynamic content and bursty traffic, so the Next.

    • js frontend can stay a thin layer that renders what the API returns.
←Back to projects/Euro Basalt
NextApp Support & Maintenance