Skip to content
EngineerSoftware
Menu
Design
English

Engineer / Software / Portfolio

A maritime platform with clear system boundaries

Architected a layered maritime platform separating a Next.js PWA frontend, a Go (Huma/Fiber) API, and a PostgreSQL function layer, keeping all business logic in the database.

Situation. NextMariner is a maritime platform covering professional networking, company reviews and educational sponsorships. The founder’s architecture contribution is recorded under the NextMariner engagement beginning in November 2025; the record does not distinguish a later employment period or establish that all of the product was delivered by Engineer ApS.

Task. As the architect, the call to make up front was where each kind of logic lived, with boundaries obvious enough to hold up under pressure instead of blurring the first time someone was in a hurry.

Action. It settled into three layers, one job each. The Next.js frontend does presentation and interactivity and nothing else. The Go API — Huma over Fiber — is deliberately thin: it routes, validates the request, applies the security filtering and orchestrates, but it holds no business logic at all. The business logic all lives in PostgreSQL functions, which assemble the full result and hand it back for the API to forward. So when a rule changes, it changes in one layer, in SQL, and the other two don’t need to know. The boundaries were written down and then enforced in review, because a convention nobody polices stops being one.

Result. The implemented architecture gives presentation, request handling and business rules separate responsibilities. The source records that separation and its rationale; it does not establish a measured improvement in delivery speed, reliability or business performance.

Cases · 2025

How the request reaches the database

  1. Frontend request

    The maritime frontend requests structured data and presents the returned JSON.

  2. Go API

    The Go API handles routing, request validation, security and the database call.

  3. PostgreSQL JSON

    Database functions produce complete JSON, which the API returns unchanged.

Implementation overview of the request path, with outcomes and measurement context kept in the case text.

Contact

Still working out what you need?

Tell us what is going wrong, or what you are trying to build. We will tell you what it would take, roughly what it would cost, and whether we are the right people for it.

From 1,400 DKK an hour, excluding VAT — and less per hour on a longer booking.

welcome@engineer.company +45 50 10 61 84 Copenhagen, Denmark