Technologies
Stacks we can start, and stacks we can keep running
The technology behind our forty-two documented projects. We often run a system for years after launch, so what we can maintain matters as much as what we can start.
- 19case studies built on Java
- 15of those on Spring Boot
- 8→21Java versions in production
- 42projects, each with its full stack listed
How we choose
Two questions decide a stack
-
What does the problem actually need?
Not what is new, and not what we used last time. The shape of the data and the load decide.
-
Who runs this in three years?
A thin hiring pool or a release cadence that breaks things turns a clever choice into a liability.
Already have a system? We work in what you have. Several platforms in our case studies were inherited, and we have run them since.
The stack
What we build with
Frontend
React for most recent work; the rest is what clients already had.
Angular
React
Vue.js
JavaScript
TypeScript
Svelte
Backend
Most of our depth: nineteen case studies on Java, fifteen of them Spring Boot.
Spring Boot
Node.js
Java
.NET
Python
Django
Mobile
Cross-platform when a shared codebase is the point, native when the device is.
Flutter
React Native
Ionic
Swift
Android
iOS
Databases
Picked for the shape of the data: relational, document or columnar.
Microsoft SQL Server
Oracle Database
MySQL
PostgreSQL
MongoDB
Elasticsearch
Cloud and infrastructure
AWS for most deployments; containers only when the workload earns them.
Microsoft Azure
Amazon Web Services
Google Cloud
Kubernetes
Beyond the logos
The parts that rarely make a logo wall
Event streaming, scheduled work, business rules, analytics and the integrations that tie a system to the outside world.
- Kafka
- Amazon SQS
- Spring Batch
- Airflow
- JBoss Drools
- KIE Server
- ClickHouse
- Neo4j
- Twilio
- Rapyd
- Salesforce
- SumSub
- KillBill
- Ethoca
- UPS
- Shippo
Tell us what you are building
A system to build, replace or rescue. We reply within one working day with who would work on it.