Skip to content
Mardi Gras Developers
Menu+

Java development

Java development: new builds, modernisation and maintenance

We develop and modernise Java systems for organisations where software is business-critical. That ranges from new services to renewing, step by step, an existing system that cannot be allowed to stop. Our experience is in enterprise environments with microservices, integrations and high security requirements.

Book an intro call

You speak to Kevin or Pascal directly. The intro call takes 30 minutes.

Updated

When to call us

  • You have a Java system that works, but nobody dares to touch it any more.
  • You want to split a monolith or move it to the cloud without downtime.
  • You are looking for senior Java capacity for a bounded project.
  • You want to add AI features to an existing Java application.

Not the right fit. There are two of us. We do not supply a team of ten; we do supply a senior who joins temporarily or a bounded project.

Characterisation test (JUnit)

@Test
void keepsLegacyRoundingOfInvoiceTotals() {
    // Pin down what the system does today, before changing anything.
    var invoice = legacyBilling.calculate(order(3, "19.99"), VAT_21);

    assertThat(invoice.total()).isEqualByComparingTo("72.56");
    assertThat(invoice.lines()).hasSize(3);
}
Before we touch legacy code, a test pins down the existing behaviour. After that the code can be renewed safely.

What you get

  • New builds

    Services and APIs with a clear architecture, automated tests and a deployment pipeline.

  • Legacy modernisation

    Renewing step by step: adding tests, updating dependencies, decoupling parts, while the system keeps running.

  • Integrations

    Integrations with payment providers, CRM and ERP systems and internal services.

  • AI in existing systems

    Search over your own data, summarisation or an agent, connected to your existing Java backend and permission model.

How we approach it

Technology

  • Java
  • JVM
  • Spring Boot
  • Maven
  • Gradle
  • PostgreSQL
  • Docker
  • Jenkins
  • AWS
  • Azure
  1. 01

    A safety net first

    Before changing legacy code, we capture the existing behaviour in tests.

  2. 02

    Renew in steps

    Every step yields a working system that can go live. No months-long side branch.

  3. 03

    Measure and operate

    Monitoring and automated deployment, so you see what happens and can roll back quickly.

Proof from our own work

Frequently asked questions

Can you take over an existing Java system?

Yes. We start with a technical review: code, dependencies, tests, deployment and risks. Then we propose a plan in which the system keeps running while it is improved.

Do we have to move from Java to Kotlin?

No. Modern Java is a fine choice. Kotlin pays off mainly for new builds or when your team wants less boilerplate and more safety in the type system. Both can coexist in one project.

How do you add AI to a Java application?

Usually as a separate service behind your existing permission model. The Java backend remains the source of truth; the AI layer searches, summarises or proposes, and only writes back through existing, controlled APIs.

Contact

Book a 30-minute intro call

Describe your question in a few sentences. Kevin or Pascal replies personally.