PubliSpeak
From POC to microservices SaaS, without losing a client or disrupting production. DDD and event-driven architecture in service of growth.
PubliSpeak started at Ipedis as a proof of concept. I built V1 from scratch, a paper-document digitization platform that became one of Ipedis's flagship products.
The platform is trusted by companies like Air Liquide, L'Oréal, Publicis and Groupe Premium through Ipedis. The challenge: evolve the architecture without disrupting service for clients who depend on it daily.
The team grew from 5 to 25 during this period. We had to scale the architecture and the organization at the same time.
The problem
A monolith starting to show its limits. The team was growing from 5 to 25 and the architecture couldn't keep up.
Every new feature became riskier. Clients depended on the platform daily, leaving zero margin for incidents.
The setup
- Role
- Lead Dev → CTO
- Duration
- ~9 years
- Pace
- 5 days/week
- Team
- 5 → 25 people
The approach
Incremental migration to 10 microservices using a DDD (Domain-Driven Design) approach. Each business domain was isolated gradually, no big bang.
RabbitMQ event bus for decoupling. No service interruption throughout the migration: clients never noticed.
Hiring and team structuring in parallel. Culture of distributed ownership, structured onboarding, continuous skill development.
Team impact
Hired and structured the team from 5 to 25 people. Built a culture of distributed ownership, structured onboarding, and continuous skill development.
Stack
Results
Architecture
Monolithic POC → 10 microservices
Team size
5 people → 25 people
Production
→ Zero major incidents
Growth
→ 10%/year for 9 years
Yanis managed to grow the product and the team simultaneously. 9 years of growth without a major incident or a missed deadline is rare.
Jackir · Managing Director, Ipedis
Patience pays off. Incremental, business-driven architecture that never sacrifices service continuity: that's how you build something that lasts.
This mission also illustrates these topics.
Architecture & tech debt
Know what to keep, simplify and modernize.
Fintech & critical product
Make financial products safer without freezing growth.
Tech team & organization
Clarify roles, seniority and ownership.
SaaS & product growth
Structure product, team and SaaS architecture without losing pace.
Delivery & quality
Reduce friction between idea, engineering, QA and production.
Reliability & security
Make incidents, risks and critical dependencies visible.
Tech governance
Turn technical uncertainty into leadership decisions.