Services
Performance engineering
Almost every performance theory we test points at the wrong place.
- up to 2 weeks → 5 minutes
- elapsed time for an onboarding process at gematik
No more waiting between steps or entering the same data twice: a new person can start work the same day.
Theories are expensive
When a system is slow, someone on the team usually has a theory. The theory is plausible, it gets implemented, and afterwards the system is about as slow as it was. The problem is rarely a lack of skill — it is a lack of measurement.
So we do not start with a change. We start with a number.
How it runs
- Measure what users experience, not only what loads the servers.
- Break the process down until it is visible which step costs what.
- Attack the largest item, not the most interesting one.
- Measure again, and put the two numbers side by side.
An example with figures
At gematik, onboarding a person took up to two weeks. Most of that was not compute time — it was waiting between steps and entering the same data more than once. After the rework the process takes five minutes. That fix would never have been found by optimising code first.
What you get
A report with measurements, a prioritised list, and — if you engage us — the work plus a second measurement. Even if you continue alone after the report, you will know where the time goes.
OUR APPROACH
Our engineering approach
Understand
Clarify requirements and context.
Engineer
Design a solution that fits the problem.
Verify
Consider integration, operations and quality.
Common questions
- How do we know the work paid off?
- From the same measurements as before. We measure, change something, measure again. Without a baseline there is no evidence, only a claim.
- Is this about server cost or waiting time?
- Usually both, but they behave differently. We establish at the outset which one matters to you, because the measures diverge.
- What if the problem is in a third-party system?
- Then that goes in the report, with measurements. Solid evidence to put in front of a supplier is often worth more than an optimisation on our side.
A change you can't afford to get wrong?
30 minutes with Benjamin Huskić, founder and engineer. Tell us about the problems, pressures, or risks that matter most right now. We'll provide an initial assessment, share relevant insights from how we've addressed similar challenges, and explore how our experience could help you move forward.