Skip to content

After assessment

Microservice architecture

Splitting a system into independent services where it is justified.

What it is

Service boundaries, contracts, queues and observability. If a modular monolith is enough, we recommend it.

Typical problem

Teams get in each other's way in one codebase, and a release requires everyone to coordinate.

What you get

  • Service boundaries
  • Contracts and queues
  • Observability

Who it is for

  • Medium-sized businesses
  • Large companies

Technologies

  • Kubernetes
  • Kafka

Examples. The stack is chosen for the task.

Rough guideline

Custom estimate

All prices here are approximate planning guides, not an offer. The final cost is set after the project is assessed and fixed in the contract.

Questions

Do you take on such projects right away?

No: first comes an assessment of requirements, risks and our ability to do the work. If a project does not suit us, we will say so directly.

Do you work with an in-house team?

Yes. This format often works best: joint decisions and knowledge transfer.

How does payment work?

Usually in stages or by time and materials. Terms are agreed individually.

Tell us what needs to be built

We will tell you whether it can be done, how and roughly for how much. No obligation.