Service / 04

Backend systems

We build clear service boundaries, robust integrations and observable backend systems that are straightforward to operate.

Start a project

orders-api — v2.4.1● 100% up

METHODPATHSTATUSP50

GET/api/orders20042 ms

POST/api/orders20188 ms

GET/api/orders/:id20012 ms

PUT/api/orders/:id20031 ms

GET/api/orders/export200214 ms

WS/events101 open—

The work

Designed for
the conditions.

01REST APIs
02Authentication and authorisation
03Background processing
04Caching and queues
05Monitoring and integrations

Process

Clear steps,
visible progress.

Map the boundaries
Identify the services, contracts and owners.
Design the contracts
Define APIs, events and failure behaviour first.
Build for failure
Timeouts, retries, queues and idempotency by default.
Operate with telemetry
Logs, metrics and traces that explain production.

The work

What you get

Documented API contracts
Event and job processing
Monitoring, logs and alerts
Load and failure testing

Operating targets

99.9%

Uptime target

Full traces

Observability

Minutes

Recovery

Live example

Edit the code. Run it. Break it.

A real, runnable slice of this work — your edits run in a sandboxed preview.

playground/backend-development.html

<h2>deploy · main → production</h2>
<p class="hint">The pipeline streams its own logs as it runs — this whole window is one deploy, from commit to edge.</p>
<div class="grid">
  <div class="stages">
    <div class="stage" id="st0"><i></i><span>BUILD</span><small></small></div>
    <div class="stage" id="st1"><i></i><span>TEST</span><small></small></div>
    <div class="stage" id="st2"><i></i><span>SHIP</span><small></small></div>
  </div>
  <div class="term"><pre id="log"><span class="cursor"></span></pre></div>
</div>
<div class="tiles">
  <div><b>12</b><small>edge regions</small></div>
  <div><b>1.2k</b><small>req / s</small></div>
  <div><b>84 ms</b><small>p95 latency</small></div>
  <div><b id="runs">1</b><small>deploys today</small></div>
</div>
<p id="status" class="idle">waiting for push…</p>
<button id="again" class="ghost">Deploy again</button>

⎇ main0 errors · 0 warningsLn 1, Col 1 · Spaces: 2 · UTF-8 · HTML · ○ idle

sandbox.nordiso.local/backend-development

sandbox idle — boots when this section scrolls into view

Technology examples

Node.js

TypeScript

PostgreSQL

Redis

Docker

Examples, not a fixed stack — chosen per project, with the team that will own it.

Node.js
TypeScript
PostgreSQL
Redis
Docker

Have something important to build?

Let’s make a good start.

Start a project

<h2>deploy · main → production</h2> <p class="hint">The pipeline streams its own logs as it runs — this whole window is one deploy, from commit to edge.</p> <div class="grid"> <div class="stages"> <div class="stage" id="st0"><i></i><span>BUILD</span><small></small></div> <div class="stage" id="st1"><i></i><span>TEST</span><small></small></div> <div class="stage" id="st2"><i></i><span>SHIP</span><small></small></div> </div> <div class="term"><pre id="log"><span class="cursor"></span></pre></div> </div> <div class="tiles"> <div><b>12</b><small>edge regions</small></div> <div><b>1.2k</b><small>req / s</small></div> <div><b>84 ms</b><small>p95 latency</small></div> <div><b id="runs">1</b><small>deploys today</small></div> </div> <p id="status" class="idle">waiting for push…</p> <button id="again" class="ghost">Deploy again</button>

Backend systems

Designed forthe conditions.

Clear steps,visible progress.

Map the boundaries

Design the contracts

Build for failure

Operate with telemetry

What you get

Edit the code. Run it. Break it.

Let’s make a good start.

Backend systems

Designed forthe conditions.

Clear steps,visible progress.

Map the boundaries

Design the contracts

Build for failure

Operate with telemetry

What you get

Edit the code. Run it. Break it.

Let’s make a good start.

Designed for
the conditions.

Clear steps,
visible progress.

Designed for
the conditions.

Clear steps,
visible progress.