Phase 1: Discovery, Requirements & Architecture Blueprint
Runtime versions, framework coupling and deployment topology are inventoried to size the re-platforming surface.
Three pillars. Twelve focused engagements.
DevNord re-platforms ageing Java EE and PHP monoliths into modular Spring Boot and PHP 8.x services on modern cloud infrastructure. Characterisation tests capture today’s behaviour before any refactor begins.
This is the service-specific architecture we design and operate. Inspect any node to see its role, the engineering or QA control around it, and how risk is contained.
Tap any node to inspect it.
Hover over a node to inspect it.
Node inspectorSelect any component to see what it does, which control protects it and how we hand it over.
An indicative 12-week cadence for a full engagement. The exact calendar, milestones and price are fixed in your EUR (€) or SEK (kr) proposal after discovery.
Indicative cadence — finalised in your fixed-scope proposal
Runtime versions, framework coupling and deployment topology are inventoried to size the re-platforming surface.
Bounded contexts are carved out behind versioned contracts while the monolith continues to serve traffic.
Manual journey tests cover locale and data edge cases while Playwright and API contracts gate each extracted service.
Traffic shifts to the new services behind a proxy; build scripts, IaC and ownership docs are transferred to your team.
Every engagement runs with the same operating model: senior squads, transparent ownership and written evidence at every gate.
Two-week sprint cadence with demoable increments and a written decision log.
Transparent Git repository ownership — repositories land in your organisation from day one.
Infrastructure-as-code (Terraform or Bicep) for every environment, reviewed and reproducible.
Fixed-scope proposals in EUR (€) or SEK (kr), with capped B2B consulting retainers when scope is still emerging.
Bilateral NDA signed before source code, architecture data or credentials are shared.
Legacy Java and PHP monoliths fail because every change shares one blast radius. DevNord captures behaviour first, then extracts bounded contexts into separately deployable services with explicit contracts. The monolith keeps earning its keep until each new slice has passed manual and automated validation.
We support upgrades to maintained Java LTS runtimes and modern PHP versions on modern cloud infrastructure, with EU-region hosting where configured. Every engagement is quoted as a fixed-scope proposal in EUR (€) or SEK (kr).
A decade of features has fused into a single WAR file or PHP codebase. Framework versions are frozen, the test suite is manual, and a small change in one module can take down unrelated workflows.
We generate a call graph across Java classes or PHP includes, record characterisation tests against the running system, and introduce an anti-corruption layer. Modules then move one at a time to containerised services with their own data.
Recorded behaviour proves the new service matches the old one before traffic moves.
Small services ship on their own schedule instead of waiting for a monolithic release train.
Supported runtimes, patched base images and policy-as-code close the CVE backlog.
These are service-specific, reviewable assets — not status reports. Your team owns each one.
Still unsure? Write to us at [email protected] — we reply in plain language, without a sales script.
Almost never. A full rewrite repeats bugs you have already learned to live with. We extract bounded contexts behind a proxy and keep proven business logic until it is safely replaced.
Yes. The strangler proxy is language-agnostic. We routinely route some paths to PHP 8.x and others to Spring Boot while the old monolith still owns the remainder.
We create characterisation tests from observed behaviour and real production traffic patterns. These become the acceptance criteria for every extracted service.
We include data ownership in the Blueprint Audit. Where needed, we introduce per-service schemas and change-data-capture patterns so domains can separate without a stop-the-world migration.
Start with a fixed-scope Blueprint Audit and get a ranked, testable extraction plan for your monolith.