Java
We build and upgrade Java services on Spring Boot 4, on Java 21 and 25 LTS. We work with Jakarta EE, Kafka and OpenTelemetry. We write the job workers and adapters your Camunda processes and IBM webMethods integrations depend on, and move older services from javax to Jakarta EE.
The task.
Your processes and integrations rest on Java services: job workers, adapters and REST services. When one of them fails, the process behind it waits.
Those services age with their framework. Spring Boot 3.5 left open-source support on 30 June 2026. Services still on Spring Boot 2 carry javax packages as well.
What we do.
- 01
Spring Boot 4 services
New services on Spring Boot 4.1, the current line. Tests are written with the code, not after it.
- 02
Java 21 and 25 LTS
We move services to a long-term support release. Java 25 is the current LTS; JDK 27 is newer but not LTS.
- 03
Jakarta EE
Services from Spring Boot 2 or Java EE move from javax to jakarta packages. We plan that change with the dependency updates.
- 04
Kafka and events
Producers and consumers on Kafka, with the schema, the retries and the owner agreed per topic.
- 05
OpenTelemetry
Traces and metrics through OpenTelemetry. One trace follows a request through every service it touches.
- 06
Workers and adapters
Camunda job workers and the Java services behind IBM webMethods integrations. Each one is written and tested as an ordinary service.
Typical engagements.
Upgrade programme
A set of services moved to Spring Boot 4 and Java 21 or 25, in short increments. Each increment ends with a tested release.
Services for a process
The job workers and adapters a new Camunda process needs, delivered with their tests.
Embedded engineers
Our engineers join your Java team. They work to your conventions and your release cycle.
Versions and dates.
From the vendors' published pages, checked on 17 October 2026.
Java 25 is the current LTS release; JDK 27 is the latest release and is not LTS.
Spring Boot 4.1 is the current line, and Spring Boot 4.0 leaves open-source support on 31 December 2026.
Spring Boot 3.5 left open-source support on 30 June 2026; its last open-source release is 3.5.16.
Spring Boot 4 requires Java 17 or later; we checked these versions on 17 October 2026.
- 30 June 2026Ended :
Spring Boot 3.5 left open-source support; the last open-source release is 3.5.16.
- 31 December 2026 :
Spring Boot 4.0 leaves open-source support; the current line is 4.1.
Is this for you?
A good fit
- Your Java services support Camunda processes or IBM webMethods integrations.
- You have services on Spring Boot 2 or 3.5 and need a dated plan.
- Your team will own the services after handover.
Not a fit
- You need people placed, with no technical lead on your side.
- You want the version raised without the tests that prove it.
- No one on your side will take the services over.
Questions.
Which Java and Spring Boot versions do you move to?
We move services to Spring Boot 4 on Java 21 or 25 LTS. We plan the move to Spring Framework 7 and Jakarta EE 11 and, for Spring Boot 2 services, the change from javax to Jakarta EE, the dependency updates and the tests. Spring Boot 3.5 left open-source support on 30 June 2026.
Why Java 21 or 25 and not JDK 27?
Java 21 and 25 are long-term support releases, and JDK 27 is not. A long-term support release gets updates for longer, so your services need fewer platform moves.
Do you write Camunda job workers in Java?
Yes, we write Camunda 8 job workers in Java, with the Camunda Java client or with Spring Boot. Each worker handles one job type and is tested on its own.
Can you trace a request across our services?
Yes, we instrument services with OpenTelemetry, so one trace follows a request through every service it touches. Your team sees where time goes and where a call fails.
Which version are you on?
Tell us the platform, the version and what has to change. We reply with questions or a proposed next step.
Talk to an architect