Architecte du Réel

Architectures

Design to last, simplify to endure. System architecture from embedded to cloud. I design solid foundations that survive technology shifts. Proven design patterns, DDD, clean architecture, pragmatic microservices, event sourcing when relevant. 30 years of critical system design.

I design simple, durable and repairable architectures, adapted to real-world constraints. My goal is not complexity, but robustness.

Every architecture starts with understanding the field. No academic schemas disconnected from operational reality. I design for the people who will live with the system — and repair it at 3 AM.

Technical approach: event storming, domain-driven design, hexagonal architecture, CQRS when relevant. Embedded stack: FreeRTOS, Zephyr, ROS2. Cloud stack: Docker, K8s, Kafka, PostgreSQL. All documented, all versioned, all tested.

« A complex system that works is invariably found to have evolved from a simple system that worked. » — John Gall

Systems I design

Engineering & Digital

Network architecture, server infrastructure, distributed systems. From design to migration.

Hybrid cloud, edge computing, HA clusters. From bare metal VMs to serverless.

Terraform, Ansible, Pulumi. CI/CD GitLab/GitHub Actions. SRE: SLI, SLO, SLAs. Disaster recovery tested every 6 months.

Marine & Energy

Onboard electrical systems, energy management, battery storage, renewable production.

Marine photovoltaic systems, LFP batteries, BMS charge management. Onboard consumption optimization.

MPPT, hybrid inverters, real-time supervision. Protocols: Modbus RTU/TCP, CAN bus for BMS. Remote monitoring via satellite.

Building & Infrastructure

Electrical installations, smart building systems, technical infrastructure.

Home automation, energy efficiency, security systems. Integration of legacy and modern equipment.

KNX, BACnet, MQTT for IoT. BMS supervision, predictive maintenance. Smart grid integration and load balancing.

My approach

1

Understanding

Before any design, I immerse myself in your context. Real needs, actual constraints.

Operational reality on the ground. Interviews with teams, analysis of existing systems, identification of pain points.

Domain-driven design workshops, event storming, bounded context mapping. Understanding the business before the technology.

2

Design

Simple solutions for complex problems. Every component justifies its existence.

No over-engineering, no technological vanity. Architecture decisions documented with trade-off analysis.

ADR (Architecture Decision Records), C4 models, threat modeling. Review by peers before implementation.

3

Implementation

Hands-on work, rigorous testing, seamless integration.

The system comes to life as designed, with no surprises. Continuous integration, automated tests.

Test-driven development, integration tests, chaos engineering. Monitoring from day one: logs, metrics, traces.

4

Documentation

Clear, comprehensive documentation. The system's memory accessible to everyone.

No dependency on a single person. Runbooks, playbooks, architecture diagrams kept up to date.

Docs-as-code: Markdown in the repo, automatic generation, doc review with code review. Every PR includes doc updates.

« The best architecture is invisible: it simply works, day after day, without demanding attention. »

Designing an architecture?

From embedded to cloud, I design simple, durable and repairable systems — remotely.

Discuss your architecture