MarByteTitle page

A backend studio of one. Poland, working worldwide.

Backends that hold under real load.

I design and build backend systems in Node.js and TypeScript, and I stay accountable for them in production.

Marcin Krysiński, MarByte Start a project

I

The engineer

MarByte is a one-person backend studio. The one person is me.

I’ve spent my career in the parts of software users never see: the APIs, databases, queues and services that have to stay correct under load. I work primarily in Node.js and TypeScript, and I care about the boring things that keep a system quiet. Clear contracts, honest error handling, and observability you can trust at 3am.

II

The practice

Everything behind the API, owned end to end.

III

The system, drawn

Figure 1. A request path, from client to telemetry. A schematic line drawing. A client (10) calls an API (12), which calls a service (14). The service reads through a cache (16) to PostgreSQL (18) and publishes to a queue (20), which a worker (22) consumes and writes back to PostgreSQL. Every component has a dashed line down to a telemetry rail (24) of logs, metrics and traces. FIG. 1 MarByte Request path Not to scale Client 10 API REST / GraphQL Node.js, TypeScript 12 Service Domain boundary 14 Cache 16 PostgreSQL 18 Queue 20 Worker 22 Telemetry Logs, metrics and traces. One correlation ID per request. 24
Fig. 1. The shape most of my work takes.
  1. 10Client.Web, mobile, or another service. It sees one contract and nothing behind it.
  2. 12API.REST or GraphQL, typed end to end, versioned without breaking clients.
  3. 14Service.Boundaries drawn along the domain, deployable on its own.
  4. 16, 18Data.Real constraints, considered indexes, and a cache with explicit invalidation.
  5. 20, 22Events.Idempotency keys, retries and dead letters, designed in from the first sprint.
  6. 24Telemetry.Every hop carries a correlation ID, so one request can be followed from 10 to 18.

IV

Method

Backends that get quieter over time.

Quiet by design

Success is a system you stop thinking about. Observable, idempotent, and calm when traffic spikes.

The best compliment a backend gets is silence: no pages, no incidents, no one asking what happened.

Direct

You brief the person who writes the code. Decisions are made by someone who has read the code.

Considered

I’d rather ship the boring, correct version than the clever one. Constraints, types and tests do the heavy lifting.

V

Your visit, traced

Every chapter you read was a span.

trace localroot visitelapsed 0 s

    Your longest span shows up here.

    Measured in your browser from scroll position and a clock. Not sent anywhere, not stored. Reload and it starts over.

    This is the work: systems that can tell you exactly what happened, span by span. I build that into every backend I ship.

    Colophon

    MarByte, 2026

    Tell me what you’re building. A short note is plenty: a new API, a rescue, a performance review. Start a project by writing to marcin_krysinski@outlook.com, and I’ll reply within two business days with next steps or a few questions.

    Studio
    MarByte
    Engineer
    Marcin Krysiński
    Based in
    Poland, working worldwide
    Elsewhere
    GitHub, LinkedIn
    Set in
    Space Grotesk and Newsreader
    Imagery
    Drawn by hand in SVG. No photographs, nothing generated.
    © 2026 Marcin Krysiński. MarByte, backend development and consulting.Back to the title page