Software Architecture & DDD
We work on event-driven architecture, senior software engineering, GCP environments, and technical structuring for ambitious products.
LRJI is Mohammed Hamdoune's consulting practice for demanding products across France, Brussels, and remote work.
Expertise
Three intervention areas for teams that need clearer architecture decisions, stronger delivery structure, or a simpler path through distributed-system complexity.
The product works, but decisions are scattered: boundaries are unclear, roadmap choices are hard to arbitrate, and technical debt is starting to drive delivery.
LRJI audits the system, names the real risks, and turns architecture discussions into decisions that a CTO, DSI, and engineering team can all use.
The team needs to ship a SaaS, prototype a risky capability, or scale a TypeScript codebase without creating a future rewrite.
LRJI shapes the domain boundaries, backend structure, delivery flow, and implementation standards needed to move fast without losing maintainability.
Features cross too many services, event flows are hard to reason about, and the operational footprint is larger than the product really needs.
LRJI reduces unnecessary runtime complexity, clarifies integration contracts, and sequences migrations without freezing the product.
Stack
The stack LRJI foregrounds is TypeScript-first, GCP-oriented, test-heavy, and architecture-led. It is chosen for systems that must stay understandable while the product and team evolve.
Backend, frontend, contracts, tests, and tooling stay aligned around one language and explicit boundaries.
Cloud Run, Kubernetes, Docker, CI/CD, and observability are used to keep delivery predictable without overbuilding the platform.
DDD, Hexagonal Architecture, tests, security, ADRs, and migration discipline are treated as delivery tools, not decoration.
The backend and API layer where most delivery decisions become concrete.
Frontend stacks for SaaS and operational products that need fast iteration and readable UI code.
Runtime, deployment, proxying, and CI/CD choices that keep environments understandable.
Persistence and asynchronous flows for product features, integrations, and distributed-system boundaries.
Patterns and decision tools used to preserve modularity, ownership, and long-term maintainability.
Testing, security posture, observability, audit practices, and AI-assisted engineering workflows.
This is the stack LRJI foregrounds publicly. Other technologies can appear in factual case-study context, but the primary positioning stays around TypeScript, GCP, architecture, testing, and maintainability.
References
Selected engagements where architecture had to improve delivery, maintainability, cost, or security without exposing confidential client details.
Technical Lead
Architect / Tech Lead
A shipped product with full-stack type safety, explicit domain boundaries, operable GCP foundations, and reusable team conventions.
Senior Backend Developer
A more readable and testable platform around a critical identity component, with clearer application boundaries.
Senior Backend Developer
Kept deliberately discreet: public detail remains limited, while the context demonstrates work on demanding identity and customer-data ecosystems.
Technical Lead
A more maintainable frontend foundation, a better coordinated team, and a migration delivered without losing SEO and accessibility concerns.
References are anonymized when client confidentiality requires it. More detail can be shared directly when appropriate.
Contact
Share the product context, architecture constraints, and decision you need to make. LRJI will reply with the most useful next step.
