Engineering Service

Microservices Architecture

We split a system into services only where it pays off, and keep the rest simple. TalentCrew runs this way today.

Capabilities

What we deliver

Service Boundaries

Deciding what deserves its own service and what stays together, so you do not run more than you need.

Shared Identity

One identity service for accounts, organisations and roles, used by every product.

API Contracts

Versioned, documented APIs between services, so an old app or service keeps working after an update.

Independent Releases

Each service builds, tests and releases on its own, from one monorepo and one CI.

Patterns

Patterns we use in production

Database per Service

Each service owns its data. No service reads another service's database.

Realtime Apart from the API

Sockets and presence in their own service, so a busy chat cannot slow down the API.

Additive Contracts

An API only gains fields, never loses them, so older mobile apps keep working after an update.

One Repository

All services in one monorepo with one language and one CI, each released on its own.

Process

How we work

1

Model

Map the business domains and who owns which data.

2

Design

Service contracts, how services talk, and where data lives.

3

Build

Build the services with tests, health checks and logs.

4

Run

Separate deploys, rollbacks and monitoring for each service.

Technology

Tools we use

TypeScriptNestJSTurborepopnpm workspacesSocket.ioMariaDBRedisKubernetes

Need a scalable architecture?

Tell us what your system does today and what it needs to handle next.