Milan · Brussels · Bucharest · Paris
EventsCareersSecurity & data protection
MDigitalGROUP
Case study · European Commission

SARI 2: 180+ screens migrated from jQuery and WebLogic to Angular and Spring Boot in six months

For the European Commission, we migrated SARI 2 — the State aid case system behind the Commission’s public State aid case search — from a jQuery front-end and Java 8 on WebLogic to Angular 22 and Spring Boot: more than 180 components and screens in almost six months.

180+components and screens migrated
~6months from kick-off to the new platform
jQuery → Angular 22front-end rebuilt on a modern, component-based framework
WebLogic → Spring Bootback-end moved off Java 8 on an application server
Context

State aid control is one of the European Commission’s core competition powers. Every measure is registered as a case — identified by an SA number — with its Member State and NUTS region, NACE economic sector, primary objective, aid instrument, legal basis, decisions, Official Journal publications and related court cases. This data is published through the public State aid case search used by governments, companies, lawyers and researchers.

The volumes are significant: in 2024 alone, Member States put in place close to 3,200 new measures under the General Block Exemption Regulation, and total State aid reached €168.2 billion, or 0.9% of EU GDP (State aid Scoreboard 2025).

SARI 2 ran on a jQuery front-end and a Java 8 back-end on Oracle WebLogic: a stack that was ageing, hard to evolve and costly to keep secure and supported.

The challenge

  • More than 180 screens and components, many with complex search, filtering and detail views
  • A rich legal domain: case types (N, NN, C, E, block exemptions), several case numbers over a case’s lifetime, decisions and court cases
  • An end-of-life platform — Java 8 on WebLogic and a jQuery front-end
  • A system in daily use that had to keep working throughout the migration
  • An aggressive timeline of around six months

How we migrated

Reuse-first and incremental: build the building blocks once, then move screens in fast, verified waves.

  1. 1

    Full inventory & mapping

    Every screen, component, business rule and data flow catalogued and mapped to its target — so nothing is lost and the scope is controlled.

  2. 2

    Reusable Angular component library

    Generic, configurable building blocks for the recurring patterns — search forms, filters, result tables, case details, decision and court-case lists — built once and reused across 180+ screens.

  3. 3

    Angular 22 front-end

    A modern single-page application with typed models, reactive state and lazy-loaded feature areas, replacing jQuery page scripts.

  4. 4

    Spring Boot back-end

    Business logic moved from Java 8 on WebLogic to Spring Boot services exposing contract-first REST APIs.

  5. 5

    Incremental waves & parity checks

    Screens migrated in waves, with functional parity verified against the legacy system before each switch.

  6. 6

    Automated quality

    CI/CD pipelines with automated tests and code quality gates, so speed never came at the expense of reliability.

How we delivered 180+ screens in six months

Speed came from architecture and organisation, not from adding people.

01

Reuse before build

The component library turned most screens into configuration and composition instead of new code.

02

Parallel streams

Front-end, back-end and testing streams working in parallel on agreed API contracts.

03

Architecture fixed up front

Target architecture, API contracts and component patterns agreed in the first weeks, so every wave followed the same blueprint.

04

Close work with the business

Case handlers validated each wave, keeping the legal logic exactly right.

Standardisation

  • One modern stackAngular and Spring Boot — the same technologies as other modern Commission platforms, easier to staff and maintain.
  • Off the application serverNo more dependency on WebLogic and Java 8, reducing licence, patching and operational overhead.
  • Maintainable by designTyped code, reusable components and automated tests make future changes faster and safer.

Technology

Before

jQueryJava 8Oracle WebLogic

Front-end

Angular 22TypeScriptRxJSReusable component library

Back-end

Spring BootJavaREST & OpenAPI

Delivery

CI/CDAutomated testingQuality gates

Outcomes

  • More than 180 components and screens migrated in almost six months
  • Legacy jQuery, Java 8 and WebLogic replaced by Angular 22 and Spring Boot
  • A reusable component library that makes new screens a matter of configuration
  • A platform that is easier to secure, maintain and evolve for the years ahead

Sources:European Commission — State aid Scoreboard 2025 · European Commission — State aid case search user guide

← Projects

Let's discuss your challenges.

Architecture, migration, AI or scaling a team — tell us what you are facing. We reply within one business day.

Start a conversation