SAP to open-stack ERP migration
Manufacturer, 500+ employees. Phased migration off SAP ERP onto an open stack with custom modules — run in stages while the plant kept working.
- 0 downtime
- 8 mo migration
- −40% on licences
Java development for systems that cannot lose a transaction
Nobody chooses Java for the syntax. They choose it because the money has to be right, the system has to run for a decade, and the next team has to be able to read it.
What we can show you
Overview
What Java is chosen for
Static types, mature transaction support and a decade of predictable releases. The cost is verbosity and setup time, and it is only worth paying for some systems.
Where Java earns its ceremony — and where it does not
Java suits domains where correctness beats speed of first delivery: finance, insurance, logistics back offices, anything with an audit trail. The type system and the ecosystem around transactions catch a class of mistakes that dynamic stacks find in production.
It is a poor trade for a three-week prototype, and it is a bad idea to add Java to a company that has no Java people. We say both of those out loud rather than selling the stack we happen to have free.
When Java is the right call
Long-lived transactional systems, teams that already run JVM infrastructure, and domains where an auditor will eventually read the logs. If your product is a fast experiment, a lighter stack gets you to the answer sooner.
Signals a Java system needs attention
- the runtime is Java 8 or 11 and upgrading keeps being postponed;
- a failed operation sometimes leaves data half-updated;
- retries occasionally create duplicate records or double charges;
- nightly batch jobs fail silently and are noticed in the morning;
- hiring for the current framework version takes months.
Price
From $7,990
Timeline
3 weeks to first release
Payment
50/50 by milestone
Comparison
Java or .NET for a corporate service
Both are right answers. The tiebreakers are your existing infrastructure, licences and who you can hire.
Criterion
.NETJava / Spring
Java.NET
Hosting
Linux or Windows, container-native
Linux or Windows on modern .NET
Licence cost in the stack
SQL Server often present
None inherent to the runtime
Ecosystem for transactions and messaging
Mature and broad
Mature and broad
Existing Windows and Active Directory estate
Integrates naturally
Works, with more configuration
Hiring pool
Large, corporate-heavy
Large, the largest in enterprise
When it wins
Microsoft estate, existing .NET team
JVM infrastructure, banking and integration-heavy domains
Scope
What we build with it
Where this stack earns its place in a project, and what we would use instead if it did not.
Transactional services
Payments, ledgers, orders and anything where a partial failure has to leave the data consistent rather than plausible.
Spring Boot APIs and integrations
Services that talk to banks, ERPs and partners, with contract tests and idempotent endpoints.
Version upgrades
Java 8 or 11 to a supported LTS, dependency by dependency, with tests as the safety net.
Batch and scheduled processing
Nightly jobs that can be re-run safely and report what they did, instead of failing quietly at 3am.
Fit
When it is the right call — and when it is not
The best stack is usually the one your team can maintain after we leave.
Right for
Enterprise and financial systems, long-lived domains, and teams that need a platform with a deep hiring pool and predictable support windows.
Not right for
A small product that needs to exist in three weeks: the ceremony costs more than it returns, and we will point you at a lighter stack.
Rates
$28–55/hour by role
Fixed builds
From $7,990
Discounts
Dedicated −10% · partners −15%
How we work
Transactions: the reason this stack is still here
The part that is specific to this stack rather than true of every project.
Why us
Why teams bring us in for this stack
Four things we can prove, not four adjectives.
Correctness before throughput
Isolation levels, idempotency and outbox patterns decided in design review. Performance tuning is easy afterwards; unwinding a double charge is not.
Upgrades with tests, not hope
Java 8 or 11 to a supported LTS, one step at a time, with characterisation tests around the flows that carry money and rollback at each step.
Contract tests on every integration
Banks, ERPs and partners change their APIs without telling you. Contract tests are how you find out before your users do.
Your repository from commit one
Code, CI and infrastructure as code in your accounts, IP assigned at delivery with a documented chain of title.
Industries
What we buildfor your industry
Java sits under the parts of logistics, manufacturing and finance where a lost record is a real loss rather than an inconvenience.
- IT companies and digital agencies
- Insurers and brokers
- Lenders and microfinance
- E-commerce
- Wholesale and distribution
- Manufacturing
- Freight and forwarding
- Clinics and medical centres
- Dental
- Car dealers and service centres
- EdTech
- Legal and consulting firms
- Equipment rental
- Real estate agencies
- Property developers
- Travel and events
- Beauty and wellness
- Construction and renovation
FAQ
Questions we get about this stack
Answered by the people who would do the work, not by a sales team.
Which Java versions do you work with?
Current LTS for new work, and upgrades from Java 8 or 11 as their own scope with their own quote. Running on an unsupported runtime is a security question, not a preference.
Spring Boot, or something else?
Spring Boot by default because the hiring pool and the documentation are deepest. Quarkus or Micronaut where startup time or memory genuinely matter, with the reason written down.
How do you handle an upgrade from Java 8?
Characterisation tests around the money flows first, then dependency-by-dependency upgrade with a rollback at each step, exactly as in legacy modernisation.
Kotlin instead of Java?
Happily, on the JVM, if your team wants it. We will flag the hiring implication rather than pretending there is none.
Will you work inside our existing codebase?
Yes, after a paid audit of the build, the dependency tree and the test coverage — the three things that decide whether an estimate is honest.
What about performance and memory?
Profiled rather than guessed: heap and GC behaviour under a realistic load, with the findings and the method in the report we hand over.
2–4×
faster on the code-writing share
in 3 weeks
from idea to MVP
230+
projects delivered
17 years
of engineering experience
Work
Work we can show you
SMARTWILL
Digital inheritance service (Web3)
AIRDEVELOPPA
Indoor air quality finder driven by sensor data
CAR5
Car-sharing app
APP.DENTAL
Cloud CRM for dental clinics
NEXORA
Warehouse and logistics management platform
As-built docs
Digital as-built documentation
EX211
Telegram Mini App for currency exchange
SMARTWILL
Digital inheritance service (Web3)
Need this stack with a senior review included?
Tell us what exists today — a green field, a legacy codebase, or a team that needs two more pairs of hands. We answer with a scope, a price and a date.
We do not take work on a stack we cannot review internally at senior level.