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

One platform, many domains: transforming delivery at Orange

How we lead a 60+ person, multi-domain delivery organisation at Orange — serving several brands with configurable web components reused across products, from the public website and the mobile app to B2B portals, and migrating the web estate to Drupal on Acquia.

60+people managed across domains
7domains: business apps, B2B, B2C, mobile, operations, infrastructure, security
Multi-brandweb components configured per brand and per product
340M+customers served by the Orange group (FY 2025)
Context

Orange serves more than 340 million customers and reported €40.4 billion in revenue in 2025. Behind that scale sits a large portfolio of business applications, B2B and B2C portals and mobile apps, supported by operations, infrastructure and security teams.

Several brands and products share the same customer journeys — on public websites, in the mobile app and in B2B portals — but each needs its own look, content and behaviour.

Over time, each domain had built its own front-ends, its own integrations and its own tooling, and the public websites ran on an ageing Drupal estate. The result: the same features implemented several times, heterogeneous technologies, and delivery costs growing with every new team.

The challenge

  • Duplicated UI components and business logic across brands, products and channels
  • The same feature needed on the public website, in the mobile app and in B2B portals, each on a different technology
  • Public websites on an ageing Drupal version, costly to maintain and evolve
  • Monolithic front-ends where one release blocked many teams
  • Web, mobile and B2B clients calling back-end services in inconsistent, chatty ways
  • Multiple frameworks and versions to maintain, patch and secure
  • Specialists spread thinly and duplicated across squads

The target architecture

A layered, federated platform where each layer is shared, versioned and owned.

  1. 1

    Shell application

    A host application that handles routing, authentication, layout and navigation, and composes domain modules at runtime.

  2. 2

    Federated domain modules

    Micro-frontends per domain, loaded through Module Federation / Native Federation and deployed independently by each team.

  3. 3

    Multi-brand web components

    A versioned library of framework-agnostic Web Components (Angular Elements) in an Nx monorepo. Design tokens switch the brand; configuration switches the product. The same component runs in Angular apps, Drupal pages, mobile app webviews and B2B portals.

  4. 4

    Drupal on Acquia

    Public websites migrated to modern Drupal on Acquia Cloud. Editors compose pages in the CMS while interactive features are delivered as the same web components used everywhere else.

  5. 5

    Backend-for-Frontend layer

    Dedicated BFFs for web, mobile and B2B that aggregate domain APIs, handle tokens and caching, and shape responses per channel.

  6. 6

    Domain services & APIs

    Contract-first REST APIs with OpenAPI specifications and generated clients, owned by the domain teams.

  7. 7

    Platform & security baseline

    Common CI/CD templates, quality gates, dependency and vulnerability scanning, observability and infrastructure standards.

Managing 60+ people without duplication

Resource management is an architecture decision. We organise teams around shared assets instead of copying skills into every squad.

01

Stream-aligned domain teams

Each domain owns its modules and APIs end to end, from B2B and B2C to mobile and business applications.

02

Shared platform & component teams

Small expert teams own the shell, the component library, the BFFs and the CI/CD platform — and serve every domain.

03

Pooled specialists

Security, infrastructure and operations experts are allocated across domains on demand instead of being duplicated.

04

One delivery rhythm

Shared planning, release trains and governance give leadership one view of capacity, priorities and cost.

Standardisation & federalisation

  • Uniform technology stackConverging applications onto one front-end framework, one BFF approach and one set of tools reduces maintenance, licences and training.
  • Federated ownershipShared modules have clear owners, contribution rules and versioning, so reuse scales without becoming a bottleneck.
  • Golden pathsProject templates and pipelines let a new application start on the standard in days, not weeks.
  • Configuration over customisationNew brands and products are enabled by design tokens and configuration, not by forking code.

Technology

Front-end

AngularWeb ComponentsAngular ElementsDesign tokensNx monorepoModule Federation / Native FederationStorybook

Web & CMS

DrupalAcquia CloudDecoupled / embedded components

BFF & APIs

Node.jsJava / Spring BootREST & OpenAPIOAuth2 / OIDC

Platform

CI/CD pipelinesContainersObservabilitySecurity scanning

Channels & brands

Public websitesMobile appB2B portalsBusiness applicationsMultiple brands

Outcomes

  • Features built once as web components and reused across brands and products — from the public website to the mobile app, B2B portals and business applications
  • New brands and products enabled by configuration and design tokens instead of new code
  • Public websites migrated to modern Drupal on Acquia, with the same components as every other channel
  • Teams release their modules independently instead of waiting for a monolithic release
  • Fewer technologies and versions to maintain, patch and secure
  • Specialists focused where they add value, with one view of capacity across 60+ people
  • Lower cost of delivery per feature as the organisation grows

Sources:Orange — 2025 full-year results (18 Feb 2026)

← 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