THE CHALLENGE
Overcoming 30 years of legacy system complexity
Bpifrance is known for its vision of ‘serving the future’. It fulfils a crucial public-interest mission to assist companies with financing, investment, and business development support, both domestically and internationally.
Over its 30-year history, including around 15 mergers, Bpifrance has accumulated a highly complex information system. Its current environment includes 700 production applications and over 1,500 production databases, managed by more than 240 agile teams.
“The mergers brought all the redundancy, legacy, and complexity you can imagine into our information system,” explained Christophe Jalady, Architect at Bpifrance. “To give you an idea, we have a single Kafka platform hosting 2,700 topics, and a central API gateway exposing about 300 APIs.”
Historically, Bpifrance relied on a fragile batch data architecture that it now refers to as the “Stone Age of data processing”. The system required extracting nightly data dumps into a massive 400 TB shared database, resulting in delays of up to five days before data could be consumed. The batch job chains were so fragile that if one failed, the entire chain collapsed.
“Real-time processing was impossible due to the architecture,” added Nizar Salhaji, Head of Domain Architecture at Bpifrance. “The operational complexity, with huge batch chains, led to a high risk of failure.”
As part of a wider modernization project, Bpifrance looked to build a data warehouse architecture using an enterprise-wide data model. However, as Mr Salhaji noted, this proved to be a “false good idea”.
“It forced unique business specifics into a single, rigid model,” he added. “That caused downstream data loss and required extensive, expensive maintenance to manage complex pipelines.”
Centralized teams also remained a massive bottleneck, and because the ingestion process still relied on nightly batch processing, true real-time data access remained impossible.
“It was also extremely expensive,” said Mr Salhaji. “It costs millions just to maintain the architecture due to its complexity.”

