About the Mission
Context The solution to be studied is based on a Java / Spring Boot microservices architecture, supplemented by a TypeScript / Angular micro-frontend approach, a DSP based on Kafka, critical mass processing (Spring Batch), and several distinct PostgreSQL databases per business domain, supplemented by 360 views and a synchronized reference base used daily for statistical or reporting purposes. The solution is containerized and runs with Podman. Each business domain is supported by approximately 4 Java applications, each placed in a separate container. This solution is developed to replace, in an iso-functional manner, another software already in place; the deployment of this solution therefore involves reusing data from the existing software. The metrics as of 01/04/2026 highlight: A significant application volume, of the order of 528,000 lines of code, including: ~475,000 Java lines, ~85,000 TypeScript / Angular lines, supplemented by SQL, CSS/SASS and various scripts; Insufficient performance in several key processes which may or may not have their origins in the architecture implemented. In this context, the SPW wishes to have an independent, objective and actionable diagnosis, making it possible to assess the relevance of architectural choices, the capacity of the solution to absorb the business load, as well as the structuring technical risks in the short and medium term. Objectives of the mission The mission aims to: Evaluate the overall performance of the application solution, both for current operation by users in transactional mode and for mass processing; Analyze the relevance of the division into microservices with regard to: Functional responsibilities, Inter‑application flows (synchronous and asynchronous), Consistency and volume constraints; Identify the root causes of observed or latent dysfunctions (performance, excessive coupling, BD contention, etc.); Evaluate transactional robustness and data consistency management in a distributed context (choreography, outbox/inbox, idempotence); Assess the level of resilience and observability (monitoring, metrics, logs, traceability, incident recovery) with regard to the SPW requirements; Produce structured, prioritized and realistic recommendations to guide development decisions (refactoring, reorganization of services, targeted optimizations). Assess the operational robustness of the solution in the face of incidents, application errors or degraded situations (exception management, behavior in the event of partial failure, continuity of service) Identify structural technical risks likely to have a lasting impact on the performance, stability or maintainability of the solution. Identify the risks and points of weakness linked to existing or planned data recovery mechanisms (quality, completeness, integrity, performance, etc.). Identify the levers to strengthen internal control of the information system and secure continuity of service in the event of a change in the sourcing method. Scope of the mission The scope covers in particular: Backend microservices; Associated PostgreSQL databases: Data models, Access, Performance, Replication and view strategies; Interservice communications, including: REST and SOAP APIs, Event exchanges via Kafka/DSP (choreography), File exchanges via FTP; Mass processing and continuous flows (Spring Batch, outbox/inbox, idempotence); The application infrastructure influences performance, to the extent that it directly impacts the observed behaviors (without an exhaustive infrastructure audit). The scope also includes, in a logic of analysis and recommendations: The planned mechanisms for data and document recovery (GED Alfresco/S3) The analysis of the impact of data recovery on: the overall performance of the system, the consistency of data in a distributed context, the robustness of processing and application chains. Excluded: Purely functional business aspects, Corrective implementations (the mission is limited to analysis and recommendations). Volumetric and metric elements As an indication, the mission must take into account the following orders of magnitude: ≈ 560,000 lines of code in total; Dominant Java / Spring Boot distribution, with a significant TypeScript / Angular base; Multiple components presenting heterogeneous volumes and varying levels of technical debt, requiring a differentiated and targeted approach in the analysis. Expected deliverables The mission will result in the production of documents written in French, delivered in an iterative manner: An executive summary for management, highlighting key findings, major risks and the main levers of action; A detailed audit report, including: Supported findings, both qualitative and quantitative; Argued and supported technical analyses; A prioritized recommendations plan, crossing the criteria of impact, effort and risk; A specific analysis relating in particular to: The maintainability and robustness of the solution in the medium term; The issues related to data recovery; The level of dependence on the service provider; A summary map of structuring technical risks, accompanied by management recommendations; A restitution support (PowerPoint type), intended for governance bodies. Prerequisites The service provider is expected to have: An independent, factual and pragmatic approach; An ability to interact with expert teams (SPW, service provider, architects); A strong capacity for synthesis, particularly for decision-making bodies; A clear orientation towards concrete and actionable recommendations, compatible with the operational constraints of the program. As part of the mission, and under the control of the SPW, the service provider will have access to: The relevant source code for carrying out the audit; Available technical and architectural documents; Documents describing data recovery/documents A dedicated application sandbox, allowing analysis and observation of the application without impact on production environments. To the testing strategy. Program governance The management of resources assigned to the mission is the responsibility of the IT project manager and the Audit Lead, who will report to the SPW on the progress of the mission on a weekly basis. Soft Skills Excellent communication in French with management bodies Capacity for critical analysis and synthesis Autonomy and rigor Pragmatic approach oriented to operational recommendations Evaluation method The preselected candidates will be invited to a qualitative interview before a digital SPW jury, aimed at assessing the adequacy of the proposed profiles, understanding of the context as well as the proposed audit methodology. The selection of the service provider will be carried out in two successive stages: Phase 1 – Analysis of applications The applications received will be analyzed on the basis of the elements provided in the offer, in particular: Administrative and contractual compliance with the ProUnity market; The adequacy of the proposed profiles with the required profiles (experience levels, key skills, expected roles); The completeness and coherence of the proposed team with regard to the mission; The presence of relevant and demonstrable references, linked to: Audits of distributed systems / microservices, Java / Spring Boot environments, Contexts with high volume and criticality. Offers not meeting the exclusion criteria explicitly mentioned in the form (in particular availability and minimum on-site presence and the expected level of experience) will be rejected. Phase 2 – Qualitative interview (pre-selected candidates) The pre-selected candidates will be invited to a qualitative interview in front of an SPW Digital jury, aimed at evaluating in a structured manner the following elements: Understanding of the context and issues Understanding of the characteristics of a critical microservices information system; Ability to identify specific issues related to: Code volume, Technical debt, Performance and resilience, Data consistency in a distributed context 2. Proposed audit methodology Clarity and relevance of the planned audit approach; Structuring the approach (framing, analysis, findings, recommendations, restitution); Ability to articulate technical analyses, factual findings and actionable recommendations; Taking into account the constraints of an existing environment (service continuity, non-regression, governance). 3. Suitability of the profiles presented Matching the roles announced and the profiles actually offered; Complementarity of skills within the team; Ability of the Audit Lead to carry out the synthesis, coordination and restitution to the steering bodies. 4. Ability to report and communicate Ability to formulate clear, supported and understandable findings; Ability to produce an executive summary adapted to a decision-making audience; Professional, pragmatic and solution-oriented attitude. Evaluation principles The evaluation will be based on an overall qualitative assessment, taking into account: The technical relevance of the proposals; Methodological maturity; The ability to deliver independent, factual and actionable analysis; Compatibility with the operational and governance expectations of the SPW. The decision will be based on the offer presenting the best overall balance between expertise, understanding of the context and quality of the proposed approach.
Required Skills
Analyse de performances PostgreSQL, Diagnostic des requêtes, index et verrous, Expérience en audit de bases de données applicatives
Practical Information
- Company: Confidential
- Location: Namur – Hybrid
- Start Date: 24 August 2026
- End Date: 30 November 2026
- Duration: 4 months
- Contract Type: Freelance / Mission
- Application Deadline: 7 June 2026