Lead Software Architect Java – Belgium (Hybrid)

Hive-X; Namen; Presencial; EUR 70.000 - 90.000; Jornada completa

Descripción de la vacante

Hive-X in Belgium is seeking an expert to evaluate the performance and architecture of a Java/Spring Boot microservices-based solution. The role involves analyzing current systems and processes, identifying weaknesses, and providing structured recommendations to improve performance and stability.

The ideal candidate should possess strong analytical skills, communicate effectively in French, and bring a pragmatic approach to enhance operational efficiency and decision-making capabilities.

Formación

• Independent and factual approach to analysis.
• Ability to interact with expert teams.
• Strong synthesis capabilities for decision making.

Responsabilidades

• Evaluate the overall performance of the application solution.
• Analyze microservices relevance for functional responsibilities.
• Identify root causes of dysfunctions and risks.
• Produce structured recommendations to guide development.

Conocimientos

Strong analytical skills

Excellent communication skills (French)

Independence and rigor

Pragmatic approach

Descripción del empleo

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: roughly 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;
• Inter-service 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 overall performance of the system, the consistency of data in a distributed context, the robustness of processing and application chains.

Expected Deliverables

• An executive summary for management, highlighting key findings, major risks and main levers of action;
• A detailed audit report, including supported findings, qualitative and quantitative analyses, and justified technical analyses;
• A prioritized recommendations plan, crossing the criteria of impact, effort and risk;
• Specific analyses addressing maintainability and robustness of the solution in the medium term, data recovery issues, dependence on the service provider, and a summary map of technical risks with recommendations;
• Support for presentation (PowerPoint type) intended for governance bodies.

Prerequisites

• Independent, factual and pragmatic approach;
• Ability to interact with expert teams (SPW, service provider, architects);
• Strong capacity for synthesis, especially for decision-making bodies;
• Clear orientation toward concrete and actionable recommendations, compatible with operational constraints of the program.

Soft Skills

• Excellent communication in French with management bodies;
• Capacity for critical analysis and synthesis;
• Autonomy and rigor;
• Pragmatic, operational-recommendation oriented approach.