31:"PublicPageHeader" 32:I[869547,["$18","$16","$19","$1a","$1b","$2c","$2d"],"$31"] 33:I[296222,["$18","$16","$19","$1a","$1b","$2c","$2d"],"RevealOnScroll"] 34:I[817357,["$18","$16","$19","$1a","$1b","$2c","$2d"],"ProjectCard"] 35:T611,flowchart TB subgraph core["Cœur de métier"] core0[" "] core0 ~~~ catalog & recipe & order & restaurant & delivery catalog["catalog
plats, stock"] recipe["recipe
recettes"] order["order
commandes, saga"] restaurant["restaurant
organisations"] delivery["delivery
livraisons"] end subgraph sup["Support"] sup0[" "] sup0 ~~~ customer & cart & review & promotion customer["customer
profil, adresses"] cart["cart
panier"] review["review
avis"] promotion["promotion
offres, codes"] end subgraph gp["Génériques — plateforme"] gp0[" "] gp0 ~~~ identity & subscription & legal & audit & reporting identity["identity
comptes, OAuth2"] subscription["subscription
formules"] legal["legal
CGU, CGV"] audit["audit
journal chaîné"] reporting["reporting
indicateurs"] end subgraph gt["Génériques — techniques"] gt0[" "] gt0 ~~~ payment & media & notification & content payment["payment
Stripe Connect"] media["media
fichiers, MinIO"] notification["notification
e-mails"] content["content
page d'accueil"] end order ~~~ sup0 review ~~~ gp0 legal ~~~ gt0 class core zoneCore class sup zoneSupporting class gp,gt zoneGeneric class catalog,recipe,order,restaurant,delivery core class customer,cart,review,promotion supporting class identity,subscription,legal,audit,reporting,payment,media,notification,content generic class core0,sup0,gp0,gt0 ghost36:T502,%%{init: {"flowchart": {"wrappingWidth": 560}}}%% flowchart TB subgraph clients["Clients"] sf["Boutique
Angular"] bo["Back office
Angular"] co["Console
Angular"] mo["App mobile
Flutter"] end edge["Caddy · TLS, en-têtes, routage"] subgraph bffs["Backends for Frontends"] sbff["storefront-bff"] abff["admin-bff"] pbff["platform-bff"] mbff["mobile-bff"] end subgraph svc["18 microservices Spring Boot — une base PostgreSQL chacun"] r1["identity · customer · catalog · recipe · media · review"] r2["cart · order · payment · notification · legal · content"] r3["restaurant · promotion · subscription · audit · reporting · delivery"] r1 ~~~ r2 ~~~ r3 end valkey[("Valkey
sessions")] kafka{{"Kafka
événements (outbox)"}} ext["Stripe · SendGrid · MinIO"] sf & bo & co & mo --> edge edge --> sbff & abff & pbff & mbff sbff & abff & pbff & mbff -->|"REST + JWT"| r1 bffs -.- valkey r3 <-.->|"événements"| kafka r3 --> ext class clients zoneClient class sf,bo,co,mo client class edge gateway class bffs zoneBff class sbff,abff,pbff,mbff bff class svc zoneService class r1,r2,r3 service class valkey data class kafka messaging class ext external37:T5ec,flowchart TB subgraph core["Core domain"] core0[" "] core0 ~~~ catalog & recipe & order & restaurant & delivery catalog["catalog
dishes, stock"] recipe["recipe
recipes"] order["order
orders, saga"] restaurant["restaurant
organisations"] delivery["delivery
deliveries"] end subgraph sup["Supporting"] sup0[" "] sup0 ~~~ customer & cart & review & promotion customer["customer
profile, addresses"] cart["cart
cart"] review["review
reviews"] promotion["promotion
offers, codes"] end subgraph gp["Generic — platform"] gp0[" "] gp0 ~~~ identity & subscription & legal & audit & reporting identity["identity
accounts, OAuth2"] subscription["subscription
plans"] legal["legal
terms"] audit["audit
chained log"] reporting["reporting
metrics"] end subgraph gt["Generic — technical"] gt0[" "] gt0 ~~~ payment & media & notification & content payment["payment
Stripe Connect"] media["media
files, MinIO"] notification["notification
e-mails"] content["content
home page"] end order ~~~ sup0 review ~~~ gp0 legal ~~~ gt0 class core zoneCore class sup zoneSupporting class gp,gt zoneGeneric class catalog,recipe,order,restaurant,delivery core class customer,cart,review,promotion supporting class identity,subscription,legal,audit,reporting,payment,media,notification,content generic class core0,sup0,gp0,gt0 ghost38:T4f8,%%{init: {"flowchart": {"wrappingWidth": 560}}}%% flowchart TB subgraph clients["Clients"] sf["Storefront
Angular"] bo["Back office
Angular"] co["Console
Angular"] mo["Mobile app
Flutter"] end edge["Caddy · TLS, headers, routing"] subgraph bffs["Backends for Frontends"] sbff["storefront-bff"] abff["admin-bff"] pbff["platform-bff"] mbff["mobile-bff"] end subgraph svc["18 Spring Boot microservices — one PostgreSQL database each"] r1["identity · customer · catalog · recipe · media · review"] r2["cart · order · payment · notification · legal · content"] r3["restaurant · promotion · subscription · audit · reporting · delivery"] r1 ~~~ r2 ~~~ r3 end valkey[("Valkey
sessions")] kafka{{"Kafka
events (outbox)"}} ext["Stripe · SendGrid · MinIO"] sf & bo & co & mo --> edge edge --> sbff & abff & pbff & mbff sbff & abff & pbff & mbff -->|"REST + JWT"| r1 bffs -.- valkey r3 <-.->|"events"| kafka r3 --> ext class clients zoneClient class sf,bo,co,mo client class edge gateway class bffs zoneBff class sbff,abff,pbff,mbff bff class svc zoneService class r1,r2,r3 service class valkey data class kafka messaging class ext externalb:["$","main",null,{"className":"mx-auto max-w-7xl px-6","children":[["$","$L32",null,{"index":"04","eyebrow":"Portfolio","title":"Des réalisations qui reflètent l'exigence","subtitle":"Applications, SaaS et plateformes conçus avec précision"}],["$","div",null,{"className":"pb-24","children":["$","div",null,{"className":"grid gap-6 sm:grid-cols-2 lg:grid-cols-3","children":[["$","$L33","291cecb6-92e0-46d2-bb17-b30d009e9396",{"delay":0,"children":["$","$L34",null,{"project":{"id":"291cecb6-92e0-46d2-bb17-b30d009e9396","slug":"terungal","githubUrl":null,"liveUrl":null,"coverImageUrl":"covers/boutique-01-accueil-1792142626070.jpg","videoUrl":null,"isFeatured":false,"isPublished":true,"position":1,"createdAt":"$D2026-10-16T08:45:14.196Z","updatedAt":"$D2026-10-18T17:53:48.182Z","translations":[{"id":"c4398832-96fd-48a6-a673-6cdb92048645","projectId":"291cecb6-92e0-46d2-bb17-b30d009e9396","languageId":"7d4b6d33-3a51-45af-8734-feedebe45c89","title":"Terungal — place de marché de cuisine sénégalaise","shortDesc":"Projet personnel à ambition professionnelle : une place de marché de plats sénégalais multi-restaurants, conçue en microservices (18 services Spring Boot, 4 BFF, 3 applications Angular) et développée avec Claude Code.","content":{"type":"doc","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Terungal","type":"text","marks":[{"type":"bold"}]},{"text":" est une plateforme de commande de plats sénégalais — thiéboudienne, yassa, maafé… — préparés à la commande et livrés. C'est un ","type":"text"},{"text":"projet personnel","type":"text","marks":[{"type":"bold"}]},{"text":" que je mène avec l'ambition d'en faire un ","type":"text"},{"text":"produit professionnel","type":"text","marks":[{"type":"bold"}]},{"text":" : partie d'une boutique unique, la plateforme est devenue une ","type":"text"},{"text":"place de marché multi-restaurants","type":"text","marks":[{"type":"bold"}]},{"text":", prête à accueillir des restaurateurs et à facturer un abonnement.","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Cette page retrace le projet en trois temps : sa ","type":"text"},{"text":"conception","type":"text","marks":[{"type":"bold"}]},{"text":" (le découpage du domaine et l'architecture microservices), son ","type":"text"},{"text":"développement","type":"text","marks":[{"type":"bold"}]},{"text":" (la structure du code, la sécurité, la qualité et la livraison) puis sa ","type":"text"},{"text":"présentation","type":"text","marks":[{"type":"bold"}]},{"text":", application par application.","type":"text"}]},{"type":"image","attrs":{"alt":"Page d'accueil de la boutique Terungal","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-01-accueil-1792142629084.jpg","title":"Figure 1 — Page d'accueil de la boutique Terungal","width":null,"height":null}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"18 microservices","type":"text","marks":[{"type":"bold"}]},{"text":" Spring Boot (Java 21), chacun avec sa base PostgreSQL","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"4 BFF","type":"text","marks":[{"type":"bold"}]},{"text":" et ","type":"text"},{"text":"3 applications Angular 22","type":"text","marks":[{"type":"bold"}]},{"text":" — boutique, back office, console — plus une application mobile Flutter en préparation","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Environ 590 tests","type":"text","marks":[{"type":"bold"}]},{"text":" unitaires et d'intégration, ","type":"text"},{"text":"80 décisions d'architecture","type":"text","marks":[{"type":"bold"}]},{"text":" consignées dans des ADR","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Conçu et développé avec ","type":"text"},{"text":"Claude Code","type":"text","marks":[{"type":"bold"}]},{"text":" comme agent de développement","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Conception","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Point de départ : un monolithe à faire évoluer","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Le projet est né d'une première application monolithique Spring Boot : un seul jar redéployé à chaque changement, un modèle de données partagé, un checkout en échec, six failles de sécurité identifiées et un seul test automatisé. Plutôt que de corriger à la marge, j'ai choisi de ","type":"text"},{"text":"reconcevoir la plateforme","type":"text","marks":[{"type":"bold"}]},{"text":" pour qu'elle puisse grandir : plusieurs restaurants, des abonnements, une console d'administration et, à terme, une application mobile.","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Découper le domaine (Domain-Driven Design)","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"La première étape a été un ","type":"text"},{"text":"inventaire","type":"text","marks":[{"type":"bold"}]},{"text":" complet du monolithe, puis un découpage en ","type":"text"},{"text":"contextes délimités","type":"text","marks":[{"type":"bold"}]},{"text":" (","type":"text"},{"text":"bounded contexts","type":"text","marks":[{"type":"italic"}]},{"text":"). Chaque contexte devient un service autonome qui possède ses données. Ils sont classés selon leur valeur : le ","type":"text"},{"text":"cœur de métier","type":"text","marks":[{"type":"bold"}]},{"text":" reçoit le plus de soin, les contextes ","type":"text"},{"text":"génériques","type":"text","marks":[{"type":"bold"}]},{"text":" reposent sur des solutions éprouvées.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 2 — Les contextes délimités de Terungal, classés en cœur de métier, support et génériques","content":"$35"}},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"La plateforme est ","type":"text"},{"text":"multi-tenant","type":"text","marks":[{"type":"bold"}]},{"text":" : le locataire est l'organisation, le périmètre le restaurant. Chaque donnée et chaque événement des contextes métier portent l'identifiant de l'organisation et du restaurant.","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Architecture cible","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Les applications ne parlent qu'à leur ","type":"text"},{"text":"BFF","type":"text","marks":[{"type":"bold"}]},{"text":" (","type":"text"},{"text":"Backend for Frontend","type":"text","marks":[{"type":"italic"}]},{"text":"), seul point d'entrée exposé derrière Caddy. Les services sont privés, ne partagent aucune base et collaborent par ","type":"text"},{"text":"événements Kafka","type":"text","marks":[{"type":"bold"}]},{"text":".","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 3 — Vue d'ensemble : clients, BFF, microservices et messagerie","content":"$36"}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Une base par service :","type":"text","marks":[{"type":"bold"}]},{"text":" aucune jointure entre services, migrations Flyway versionnées.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Pas d'appel direct entre services :","type":"text","marks":[{"type":"bold"}]},{"text":" la collaboration passe uniquement par des événements.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"BFF par application :","type":"text","marks":[{"type":"bold"}]},{"text":" chaque front-end a une API taillée pour ses écrans et ne voit jamais les jetons.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Des événements fiables : outbox et idempotence","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Un événement ne doit jamais être perdu ni appliqué deux fois. Chaque service écrit l'agrégat et le message dans la ","type":"text"},{"text":"même transaction","type":"text","marks":[{"type":"bold"}]},{"text":" (","type":"text"},{"text":"transactional outbox","type":"text","marks":[{"type":"italic"}]},{"text":") ; un relais publie ensuite dans l'ordre. Côté consommateur, chaque message déjà traité est ignoré.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 4 — Publication d'un événement via l'outbox et consommation idempotente","content":"sequenceDiagram\n participant UC as Use case (transaction)\n participant DB as Base du producteur\n participant R as Relais outbox\n participant K as Kafka\n participant C as Consommateur\n UC->>DB: agrégat + message outbox (même transaction)\n R->>DB: lit les messages en attente\n R->>K: publie dans l'ordre\n R->>DB: marque PUBLISHED\n K->>C: message\n C->>C: déjà traité ? ignoré (idempotence)\n Note over C: échec : 5 reprises puis topic .dlt"}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"La commande : une saga","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Le checkout, en échec dans le monolithe, a été reconstruit comme une ","type":"text"},{"text":"saga orchestrée","type":"text","marks":[{"type":"bold"}]},{"text":" par le service des commandes : paiement, réservation du stock et vidage du panier s'enchaînent par événements, avec des compensations (annulation, remboursement) en cas d'échec.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 5 — Saga du checkout et ses compensations","content":"sequenceDiagram\n participant O as order (orchestrateur)\n participant P as payment\n participant C as catalog\n participant K as cart\n O->>P: PaymentRequested\n P-->>O: PaymentCompleted\n O->>C: OrderPaid\n O->>K: OrderPaid (vider le panier)\n C-->>O: StockReserved\n Note over O: commande en préparation\n alt paiement refusé ou délai dépassé\n P-->>O: PaymentFailed\n O->>P: OrderCancelled\n else stock insuffisant après paiement\n C-->>O: StockRejected\n O->>P: RefundRequested\n P-->>O: PaymentRefunded\n end"}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Migrer sans tout arrêter","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"La migration suit le motif ","type":"text"},{"text":"strangler","type":"text","marks":[{"type":"bold"}]},{"text":" : le BFF route chaque route soit vers le monolithe, soit vers le service déjà migré, et les données du monolithe sont répliquées vers les services (Debezium et Kafka). Les contextes ont été extraits par vagues, du moins risqué au plus central.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 6 — Pendant la transition : le monolithe et les services migrés coexistent","content":"flowchart LR\n fronts[\"Frontends Angular\"] --> bff[\"BFF
routage par route\"]\n bff -->|\"routes non migrées\"| legacy[\"Monolithe
inchangé\"]\n bff -->|\"routes migrées\"| svc[\"Services migrés\"]\n legacy --> ldb[(\"Base legacy\")]\n ldb -->|\"réplication (CDC)\"| dbz[\"Debezium\"]\n dbz --> kafka{{\"Kafka\"}}\n kafka --> svc\n svc --> sdb[(\"Bases des services\")]\n class fronts client\n class bff bff\n class legacy legacy\n class ldb,sdb data\n class dbz,kafka messaging\n class svc service"}},{"type":"mermaidBlock","attrs":{"caption":"Figure 7 — Ordre d'extraction des contextes, par vagues","content":"flowchart LR\n v0[\"Vague 0
socle transverse\"] --> v1[\"Vague 1
review (pilote)\"]\n v1 --> v2[\"Vague 2
catalog + media\"]\n v2 --> v3[\"Vague 3
recipe\"]\n v3 --> v4[\"Vague 4
cart, order,
payment, notification\"]\n v4 --> v5[\"Vague 5
identity, customer\"]\n v5 --> f[\"Arrêt du
monolithe\"]\n class v0 generic\n class v1,v2,v3,v4,v5 service\n class f core"}},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Chaque choix structurant — données par service, messagerie, saga, sécurité, multi-tenancy, déploiement — est consigné dans un ","type":"text"},{"text":"ADR","type":"text","marks":[{"type":"bold"}]},{"text":" (","type":"text"},{"text":"Architecture Decision Record","type":"text","marks":[{"type":"italic"}]},{"text":") : ","type":"text"},{"text":"80 décisions","type":"text","marks":[{"type":"bold"}]},{"text":" documentées à ce jour.","type":"text"}]},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Développement","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Un service, trois modules : architecture hexagonale","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Chaque microservice suit la même structure, inspirée de l'","type":"text"},{"text":"architecture hexagonale","type":"text","marks":[{"type":"bold"}]},{"text":" et de la ","type":"text"},{"text":"Clean Architecture","type":"text","marks":[{"type":"bold"}]},{"text":" : trois modules Maven ","type":"text"},{"text":"domain","type":"text","marks":[{"type":"code"}]},{"text":", ","type":"text"},{"text":"application","type":"text","marks":[{"type":"code"}]},{"text":" et ","type":"text"},{"text":"infrastructure","type":"text","marks":[{"type":"code"}]},{"text":". Les dépendances pointent toujours vers le domaine, écrit en Java pur, sans framework.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 8 — Structure d'un microservice : adapters, ports, use cases et domaine","content":"flowchart LR\n subgraph in[\"infrastructure — adapters entrants\"]\n web[\"Contrôleur REST\"]\n kin[\"Consommateur Kafka
idempotent\"]\n end\n subgraph app[\"application\"]\n pin[\"Ports d'entrée
use cases\"]\n svc[\"Services applicatifs\"]\n pout[\"Ports de sortie
repository, publisher\"]\n end\n subgraph dom[\"domain — Java pur\"]\n agg[\"Agrégats, value objects,
événements de domaine\"]\n end\n subgraph out[\"infrastructure — adapters sortants\"]\n jpa[\"JPA · PostgreSQL · Flyway\"]\n ob[\"Outbox → Kafka\"]\n end\n web & kin --> pin --> svc --> agg\n svc --> pout\n jpa & ob -.->|\"implémentent\"| pout\n class in zoneBff\n class app zoneService\n class dom zoneCore\n class out zoneGeneric\n class web,kin bff\n class pin,svc,pout service\n class agg core\n class jpa,ob data"}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Règles vérifiées automatiquement","type":"text","marks":[{"type":"bold"}]},{"text":" (ArchUnit) : un contrôleur n'appelle que des ports d'entrée, le domaine ne dépend de rien.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Conventions communes :","type":"text","marks":[{"type":"bold"}]},{"text":" nommage, erreurs REST au format RFC 9457, clé d'idempotence sur les créations sensibles.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Modules partagés","type":"text","marks":[{"type":"bold"}]},{"text":" pour la messagerie (contrats d'événements versionnés, outbox, consommateurs idempotents).","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Sécurité","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"L'identité est centralisée dans ","type":"text"},{"text":"identity-service","type":"text","marks":[{"type":"code"}]},{"text":" (OAuth2 / OIDC). Les ","type":"text"},{"text":"jetons ne quittent jamais les BFF","type":"text","marks":[{"type":"bold"}]},{"text":" : le navigateur ne reçoit qu'un cookie de session, et chaque service revérifie le JWT et les droits sur la ressource demandée.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 9 — Authentification : le BFF garde les jetons, chaque service vérifie les droits","content":"sequenceDiagram\n participant N as Navigateur\n participant B as BFF\n participant I as identity-service\n participant S as Service métier\n N->>B: connexion\n B->>I: OAuth2 / OIDC\n I-->>B: jetons (JWT signés)\n B-->>N: cookie de session SameSite\n Note over B: les jetons restent côté BFF (Valkey)\n N->>B: requête\n B->>S: appel REST avec le JWT\n S->>S: vérifie la signature (JWKS) et les droits sur la ressource"}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Contrôle d'accès par rôles et par périmètre (organisation, restaurant).","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Journal d'audit ","type":"text"},{"text":"chaîné","type":"text","marks":[{"type":"bold"}]},{"text":" : chaque action sensible est scellée avec l'empreinte de la précédente.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Documents légaux versionnés : la version acceptée est enregistrée avec chaque commande.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Front-ends","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Trois applications ","type":"text"},{"text":"Angular 22","type":"text","marks":[{"type":"bold"}]},{"text":" partagent une bibliothèque commune : la ","type":"text"},{"text":"boutique","type":"text","marks":[{"type":"bold"}]},{"text":" des clients, le ","type":"text"},{"text":"back office","type":"text","marks":[{"type":"bold"}]},{"text":" des restaurants et la ","type":"text"},{"text":"console","type":"text","marks":[{"type":"bold"}]},{"text":" de la plateforme. L'état est géré avec les ","type":"text"},{"text":"signals","type":"text","marks":[{"type":"bold"}]},{"text":" (NgRx Signals) et l'interface avec ","type":"text"},{"text":"Tailwind CSS 4","type":"text","marks":[{"type":"bold"}]},{"text":". Une application mobile ","type":"text"},{"text":"Flutter","type":"text","marks":[{"type":"bold"}]},{"text":", avec son propre BFF, est en préparation.","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Qualité, livraison et exploitation","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Tests :","type":"text","marks":[{"type":"bold"}]},{"text":" environ 590 tests unitaires et d'intégration (Testcontainers) et 76 tests de caractérisation du monolithe.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Livraison :","type":"text","marks":[{"type":"bold"}]},{"text":" une image Docker et un pipeline par application ; chaque service se déploie indépendamment.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Environnements :","type":"text","marks":[{"type":"bold"}]},{"text":" démarrage léger (infrastructure dans Docker) ou complet, par profils Docker Compose.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Observabilité :","type":"text","marks":[{"type":"bold"}]},{"text":" traces de bout en bout (OpenTelemetry), journaux JSON corrélés, métriques métier et alertes dans Grafana.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Développé avec Claude Code","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Terungal a été conçu et développé avec ","type":"text"},{"text":"Claude Code","type":"text","marks":[{"type":"bold"}]},{"text":" comme agent de développement, de l'inventaire du monolithe jusqu'aux applications Angular. Chaque étape de la migration est guidée par un ","type":"text"},{"text":"prompt versionné","type":"text","marks":[{"type":"bold"}]},{"text":" dans le dépôt, les conventions sont fixées dans des fichiers ","type":"text"},{"text":"CLAUDE.md","type":"text","marks":[{"type":"code"}]},{"text":" et chaque choix structurant fait l'objet d'un ADR. Le code produit est ","type":"text"},{"text":"relu, testé et validé","type":"text","marks":[{"type":"bold"}]},{"text":" avant intégration.","type":"text"}]},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Présentation","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"La boutique","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"La boutique accompagne le client du choix du plat jusqu'à la commande, et s'adapte à lui une fois connecté.","type":"text"}]},{"type":"image","attrs":{"alt":"Collections et « plats habituels » du client connecté","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-02-collections-habituels-1792142632033.jpg","title":"Figure 10 — Collections et « plats habituels » du client connecté","width":null,"height":null}},{"type":"image","attrs":{"alt":"Catalogue : plats les plus commandés, notes, prix et commandes du mois","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-03-catalogue-1792142635071.jpg","title":"Figure 11 — Catalogue : plats les plus commandés, notes, prix et commandes du mois","width":null,"height":null}},{"type":"image","attrs":{"alt":"Fiche d'un plat : note, avis et favoris","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-04-fiche-plat-1792142638128.jpg","title":"Figure 12 — Fiche d'un plat : note, avis et favoris","width":null,"height":null}},{"type":"image","attrs":{"alt":"Fiche plat : bloc de commande — aucun débit avant la validation du paiement","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-05-commande-1792142643598.jpg","title":"Figure 13 — Fiche plat : bloc de commande — aucun débit avant la validation du paiement","width":null,"height":null}},{"type":"image","attrs":{"alt":"Recette publiée par le restaurant : préparation, cuisson, portions, difficulté","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-06-recette-1792142645289.jpg","title":"Figure 14 — Recette publiée par le restaurant : préparation, cuisson, portions, difficulté","width":null,"height":null}},{"type":"image","attrs":{"alt":"Place de marché : restaurants proches et ouverts maintenant","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-07-place-de-marche-1792142648082.jpg","title":"Figure 15 — Place de marché : restaurants proches et ouverts maintenant","width":null,"height":null}},{"type":"image","attrs":{"alt":"Espace client : favoris dans tous les restaurants","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-08-favoris-1792142650671.jpg","title":"Figure 16 — Espace client : favoris dans tous les restaurants","width":null,"height":null}},{"type":"image","attrs":{"alt":"Espace client : préférences alimentaires (régimes et allergènes)","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-09-preferences-1792142653723.jpg","title":"Figure 17 — Espace client : préférences alimentaires (régimes et allergènes)","width":null,"height":null}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Le back office des restaurants","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Chaque restaurant pilote son activité depuis son back office : service du jour, catalogue, offres, horaires et vitrine de sa boutique.","type":"text"}]},{"type":"image","attrs":{"alt":"Back office : l'activité du jour et l'état du stock","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-01-aujourdhui-1792142163956.jpg","title":"Figure 18 — Back office : l'activité du jour et l'état du stock","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office : catalogue des plats, prix et stocks","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-02-produits-1792142164832.jpg","title":"Figure 19 — Back office : catalogue des plats, prix et stocks","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office : offres, remises et codes promo","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-03-offres-1792142167413.jpg","title":"Figure 20 — Back office : offres, remises et codes promo","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office : horaires, jours fériés et fermetures","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-04-horaires-1792142170495.jpg","title":"Figure 21 — Back office : horaires, jours fériés et fermetures","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office : collections affichées sur la boutique","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-05-collections-1792142173469.jpg","title":"Figure 22 — Back office : collections affichées sur la boutique","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office : paramétrage de la page d'accueil avec aperçu en direct","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-06-parametrage-1792142176515.jpg","title":"Figure 23 — Back office : paramétrage de la page d'accueil avec aperçu en direct","width":null,"height":null}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"La console de la plateforme","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"La console, réservée aux administrateurs, pilote la place de marché dans son ensemble : activité, onboarding des restaurateurs, modèle économique, conformité et traçabilité.","type":"text"}]},{"type":"image","attrs":{"alt":"Console : tableau de bord — volume d'affaires, commissions, revenu récurrent","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-01-tableau-de-bord-1792141643699.jpg","title":"Figure 24 — Console : tableau de bord — volume d'affaires, commissions, revenu récurrent","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console : formules d'abonnement versionnées","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-02-formules-1792141646659.jpg","title":"Figure 25 — Console : formules d'abonnement versionnées","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console : documents légaux versionnés de la plateforme","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-03-documents-legaux-1792141649672.jpg","title":"Figure 26 — Console : documents légaux versionnés de la plateforme","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console : référentiels communs à tous les restaurants","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-04-referentiels-1792141652727.jpg","title":"Figure 27 — Console : référentiels communs à tous les restaurants","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console : journal d'audit chaîné et vérifiable","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-05-journal-audit-1792141655734.jpg","title":"Figure 28 — Console : journal d'audit chaîné et vérifiable","width":null,"height":null}},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Bilan et perspectives","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Du monolithe à la plateforme :","type":"text","marks":[{"type":"bold"}]},{"text":" une application déployable devenue 18 services, 4 BFF et 3 front-ends, chacun livré indépendamment.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Commande fiabilisée :","type":"text","marks":[{"type":"bold"}]},{"text":" le checkout passe par une saga commande, paiement et stock.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Sécurité :","type":"text","marks":[{"type":"bold"}]},{"text":" les six failles du monolithe sont corrigées et vérifiées.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Nouvelles capacités :","type":"text","marks":[{"type":"bold"}]},{"text":" multi-restaurants, abonnements, offres, console de la plateforme.","type":"text"}]}]}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Prochaines étapes vers un produit professionnel : la ","type":"text"},{"text":"mise en production","type":"text","marks":[{"type":"bold"}]},{"text":" et l'arrêt du monolithe, le ","type":"text"},{"text":"suivi des livraisons en temps réel","type":"text","marks":[{"type":"bold"}]},{"text":" et l'","type":"text"},{"text":"application mobile","type":"text","marks":[{"type":"bold"}]},{"text":" cliente.","type":"text"}]}]},"stack":["Java","Spring Boot","Angular","TypeScript","Tailwind CSS","PostgreSQL","Kafka","Docker","Stripe","MinIO","Valkey","Caddy","OpenTelemetry","Grafana","Flutter","Testcontainers","Claude Code"]},{"id":"8b956efb-9da6-40d2-b76c-3544c58f769a","projectId":"291cecb6-92e0-46d2-bb17-b30d009e9396","languageId":"f9cd6b7f-f1fe-409d-94ca-a21247f7601e","title":"Terungal — Senegalese food marketplace","shortDesc":"A personal project with professional ambitions: a multi-restaurant marketplace for Senegalese dishes, designed as microservices (18 Spring Boot services, 4 BFFs, 3 Angular apps) and built with Claude Code.","content":{"type":"doc","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Terungal","type":"text","marks":[{"type":"bold"}]},{"text":" is an ordering platform for Senegalese dishes — thieboudienne, yassa, maafe… — cooked to order and delivered. It is a ","type":"text"},{"text":"personal project","type":"text","marks":[{"type":"bold"}]},{"text":" that I am building with the ambition of turning it into a ","type":"text"},{"text":"professional product","type":"text","marks":[{"type":"bold"}]},{"text":": it started as a single shop and became a ","type":"text"},{"text":"multi-restaurant marketplace","type":"text","marks":[{"type":"bold"}]},{"text":", ready to onboard restaurant owners and bill them a subscription.","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"This page tells the story in three parts: its ","type":"text"},{"text":"design","type":"text","marks":[{"type":"bold"}]},{"text":" (domain split and microservices architecture), its ","type":"text"},{"text":"development","type":"text","marks":[{"type":"bold"}]},{"text":" (code structure, security, quality and delivery) and its ","type":"text"},{"text":"presentation","type":"text","marks":[{"type":"bold"}]},{"text":", application by application.","type":"text"}]},{"type":"image","attrs":{"alt":"Terungal storefront home page","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-01-accueil-1792142629084.jpg","title":"Figure 1 — Terungal storefront home page","width":null,"height":null}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"18 Spring Boot microservices","type":"text","marks":[{"type":"bold"}]},{"text":" (Java 21), each with its own PostgreSQL database","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"4 BFFs","type":"text","marks":[{"type":"bold"}]},{"text":" and ","type":"text"},{"text":"3 Angular 22 applications","type":"text","marks":[{"type":"bold"}]},{"text":" — storefront, back office, console — plus a Flutter mobile app in progress","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"About 590 unit and integration tests","type":"text","marks":[{"type":"bold"}]},{"text":", ","type":"text"},{"text":"80 architecture decisions","type":"text","marks":[{"type":"bold"}]},{"text":" recorded as ADRs","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Designed and built with ","type":"text"},{"text":"Claude Code","type":"text","marks":[{"type":"bold"}]},{"text":" as the development agent","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Design","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Starting point: a monolith that had to evolve","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"The project grew out of a first Spring Boot monolith: a single jar redeployed on every change, a shared data model, a failing checkout, six identified security flaws and a single automated test. Rather than patching it, I chose to ","type":"text"},{"text":"redesign the platform","type":"text","marks":[{"type":"bold"}]},{"text":" so it could grow: several restaurants, subscriptions, an admin console and, eventually, a mobile app.","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Splitting the domain (Domain-Driven Design)","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"The first step was a full ","type":"text"},{"text":"inventory","type":"text","marks":[{"type":"bold"}]},{"text":" of the monolith, then a split into ","type":"text"},{"text":"bounded contexts","type":"text","marks":[{"type":"bold"}]},{"text":". Each context becomes an autonomous service that owns its data. They are ranked by value: the ","type":"text"},{"text":"core domain","type":"text","marks":[{"type":"bold"}]},{"text":" gets the most care, while ","type":"text"},{"text":"generic","type":"text","marks":[{"type":"bold"}]},{"text":" contexts rely on proven solutions.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 2 — Terungal's bounded contexts, ranked as core, supporting and generic","content":"$37"}},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"The platform is ","type":"text"},{"text":"multi-tenant","type":"text","marks":[{"type":"bold"}]},{"text":": the tenant is the organisation, the scope is the restaurant. Every record and event of the business contexts carries the organisation and restaurant identifiers.","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Target architecture","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Applications only talk to their ","type":"text"},{"text":"BFF","type":"text","marks":[{"type":"bold"}]},{"text":" (","type":"text"},{"text":"Backend for Frontend","type":"text","marks":[{"type":"italic"}]},{"text":"), the single entry point exposed behind Caddy. Services are private, share no database and collaborate through ","type":"text"},{"text":"Kafka events","type":"text","marks":[{"type":"bold"}]},{"text":".","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 3 — Overview: clients, BFFs, microservices and messaging","content":"$38"}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"One database per service:","type":"text","marks":[{"type":"bold"}]},{"text":" no cross-service joins, versioned Flyway migrations.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"No direct calls between services:","type":"text","marks":[{"type":"bold"}]},{"text":" collaboration only goes through events.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"One BFF per application:","type":"text","marks":[{"type":"bold"}]},{"text":" each front-end gets an API shaped for its screens and never sees the tokens.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Reliable events: outbox and idempotency","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"An event must never be lost or applied twice. Each service writes the aggregate and the message in the ","type":"text"},{"text":"same transaction","type":"text","marks":[{"type":"bold"}]},{"text":" (","type":"text"},{"text":"transactional outbox","type":"text","marks":[{"type":"italic"}]},{"text":"); a relay then publishes them in order. On the consumer side, any message already processed is ignored.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 4 — Publishing an event through the outbox, with idempotent consumption","content":"sequenceDiagram\n participant UC as Use case (transaction)\n participant DB as Producer database\n participant R as Outbox relay\n participant K as Kafka\n participant C as Consumer\n UC->>DB: aggregate + outbox message (same transaction)\n R->>DB: reads pending messages\n R->>K: publishes in order\n R->>DB: marks PUBLISHED\n K->>C: message\n C->>C: already processed? ignored (idempotency)\n Note over C: failure: 5 retries, then .dlt topic"}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Ordering as a saga","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"The checkout, broken in the monolith, was rebuilt as a ","type":"text"},{"text":"saga orchestrated","type":"text","marks":[{"type":"bold"}]},{"text":" by the order service: payment, stock reservation and cart clean-up are chained through events, with compensations (cancellation, refund) when something fails.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 5 — Checkout saga and its compensations","content":"sequenceDiagram\n participant O as order (orchestrator)\n participant P as payment\n participant C as catalog\n participant K as cart\n O->>P: PaymentRequested\n P-->>O: PaymentCompleted\n O->>C: OrderPaid\n O->>K: OrderPaid (empty the cart)\n C-->>O: StockReserved\n Note over O: order being prepared\n alt payment refused or timed out\n P-->>O: PaymentFailed\n O->>P: OrderCancelled\n else not enough stock after payment\n C-->>O: StockRejected\n O->>P: RefundRequested\n P-->>O: PaymentRefunded\n end"}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Migrating without stopping","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"The migration follows the ","type":"text"},{"text":"strangler","type":"text","marks":[{"type":"bold"}]},{"text":" pattern: the BFF routes each route either to the monolith or to the already migrated service, and the monolith's data is replicated to the services (Debezium and Kafka). Contexts were extracted in waves, from the least risky to the most central.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 6 — During the transition: the monolith and migrated services coexist","content":"flowchart LR\n fronts[\"Angular front-ends\"] --> bff[\"BFF
per-route routing\"]\n bff -->|\"routes not migrated\"| legacy[\"Monolith
unchanged\"]\n bff -->|\"migrated routes\"| svc[\"Migrated services\"]\n legacy --> ldb[(\"Legacy database\")]\n ldb -->|\"replication (CDC)\"| dbz[\"Debezium\"]\n dbz --> kafka{{\"Kafka\"}}\n kafka --> svc\n svc --> sdb[(\"Service databases\")]\n class fronts client\n class bff bff\n class legacy legacy\n class ldb,sdb data\n class dbz,kafka messaging\n class svc service"}},{"type":"mermaidBlock","attrs":{"caption":"Figure 7 — Order in which the contexts were extracted, wave by wave","content":"flowchart LR\n v0[\"Wave 0
shared foundation\"] --> v1[\"Wave 1
review (pilot)\"]\n v1 --> v2[\"Wave 2
catalog + media\"]\n v2 --> v3[\"Wave 3
recipe\"]\n v3 --> v4[\"Wave 4
cart, order,
payment, notification\"]\n v4 --> v5[\"Wave 5
identity, customer\"]\n v5 --> f[\"Monolith
shutdown\"]\n class v0 generic\n class v1,v2,v3,v4,v5 service\n class f core"}},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Every structural choice — data per service, messaging, saga, security, multi-tenancy, deployment — is recorded in an ","type":"text"},{"text":"ADR","type":"text","marks":[{"type":"bold"}]},{"text":" (","type":"text"},{"text":"Architecture Decision Record","type":"text","marks":[{"type":"italic"}]},{"text":"): ","type":"text"},{"text":"80 decisions","type":"text","marks":[{"type":"bold"}]},{"text":" documented so far.","type":"text"}]},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Development","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"One service, three modules: hexagonal architecture","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Every microservice follows the same structure, inspired by ","type":"text"},{"text":"hexagonal architecture","type":"text","marks":[{"type":"bold"}]},{"text":" and ","type":"text"},{"text":"Clean Architecture","type":"text","marks":[{"type":"bold"}]},{"text":": three Maven modules ","type":"text"},{"text":"domain","type":"text","marks":[{"type":"code"}]},{"text":", ","type":"text"},{"text":"application","type":"text","marks":[{"type":"code"}]},{"text":" and ","type":"text"},{"text":"infrastructure","type":"text","marks":[{"type":"code"}]},{"text":". Dependencies always point towards the domain, written in plain Java with no framework.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 8 — Structure of a microservice: adapters, ports, use cases and domain","content":"flowchart LR\n subgraph in[\"infrastructure — inbound adapters\"]\n web[\"REST controller\"]\n kin[\"Kafka consumer
idempotent\"]\n end\n subgraph app[\"application\"]\n pin[\"Inbound ports
use cases\"]\n svc[\"Application services\"]\n pout[\"Outbound ports
repository, publisher\"]\n end\n subgraph dom[\"domain — plain Java\"]\n agg[\"Aggregates, value objects,
domain events\"]\n end\n subgraph out[\"infrastructure — outbound adapters\"]\n jpa[\"JPA · PostgreSQL · Flyway\"]\n ob[\"Outbox → Kafka\"]\n end\n web & kin --> pin --> svc --> agg\n svc --> pout\n jpa & ob -.->|\"implement\"| pout\n class in zoneBff\n class app zoneService\n class dom zoneCore\n class out zoneGeneric\n class web,kin bff\n class pin,svc,pout service\n class agg core\n class jpa,ob data"}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Rules checked automatically","type":"text","marks":[{"type":"bold"}]},{"text":" (ArchUnit): a controller only calls inbound ports, the domain depends on nothing.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Shared conventions:","type":"text","marks":[{"type":"bold"}]},{"text":" naming, RFC 9457 REST errors, an idempotency key on sensitive creations.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Shared modules","type":"text","marks":[{"type":"bold"}]},{"text":" for messaging (versioned event contracts, outbox, idempotent consumers).","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Security","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Identity is centralised in ","type":"text"},{"text":"identity-service","type":"text","marks":[{"type":"code"}]},{"text":" (OAuth2 / OIDC). ","type":"text"},{"text":"Tokens never leave the BFFs","type":"text","marks":[{"type":"bold"}]},{"text":": the browser only gets a session cookie, and every service re-checks the JWT and the rights on the requested resource.","type":"text"}]},{"type":"mermaidBlock","attrs":{"caption":"Figure 9 — Authentication: the BFF keeps the tokens, every service checks the rights","content":"sequenceDiagram\n participant N as Browser\n participant B as BFF\n participant I as identity-service\n participant S as Business service\n N->>B: sign in\n B->>I: OAuth2 / OIDC\n I-->>B: tokens (signed JWTs)\n B-->>N: SameSite session cookie\n Note over B: tokens stay in the BFF (Valkey)\n N->>B: request\n B->>S: REST call with the JWT\n S->>S: checks the signature (JWKS) and rights on the resource"}},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Role- and scope-based access control (organisation, restaurant).","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"A ","type":"text"},{"text":"chained","type":"text","marks":[{"type":"bold"}]},{"text":" audit log: every sensitive action is sealed with the hash of the previous one.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Versioned legal documents: the accepted version is stored with each order.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Front-ends","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Three ","type":"text"},{"text":"Angular 22","type":"text","marks":[{"type":"bold"}]},{"text":" applications share a common library: the customers' ","type":"text"},{"text":"storefront","type":"text","marks":[{"type":"bold"}]},{"text":", the restaurants' ","type":"text"},{"text":"back office","type":"text","marks":[{"type":"bold"}]},{"text":" and the platform ","type":"text"},{"text":"console","type":"text","marks":[{"type":"bold"}]},{"text":". State is managed with ","type":"text"},{"text":"signals","type":"text","marks":[{"type":"bold"}]},{"text":" (NgRx Signals) and the UI is built with ","type":"text"},{"text":"Tailwind CSS 4","type":"text","marks":[{"type":"bold"}]},{"text":". A ","type":"text"},{"text":"Flutter","type":"text","marks":[{"type":"bold"}]},{"text":" mobile app, with its own BFF, is in progress.","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Quality, delivery and operations","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Tests:","type":"text","marks":[{"type":"bold"}]},{"text":" about 590 unit and integration tests (Testcontainers) and 76 characterisation tests of the monolith.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Delivery:","type":"text","marks":[{"type":"bold"}]},{"text":" one Docker image and one pipeline per application; each service is deployed independently.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Environments:","type":"text","marks":[{"type":"bold"}]},{"text":" a lightweight setup (infrastructure in Docker) or a full one through Docker Compose profiles.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Observability:","type":"text","marks":[{"type":"bold"}]},{"text":" end-to-end traces (OpenTelemetry), correlated JSON logs, business metrics and alerts in Grafana.","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"Built with Claude Code","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Terungal was designed and built with ","type":"text"},{"text":"Claude Code","type":"text","marks":[{"type":"bold"}]},{"text":" as its development agent, from the inventory of the monolith to the Angular applications. Each migration step is driven by a ","type":"text"},{"text":"prompt versioned","type":"text","marks":[{"type":"bold"}]},{"text":" in the repository, conventions live in ","type":"text"},{"text":"CLAUDE.md","type":"text","marks":[{"type":"code"}]},{"text":" files and every structural choice has its ADR. Generated code is ","type":"text"},{"text":"reviewed, tested and validated","type":"text","marks":[{"type":"bold"}]},{"text":" before merging.","type":"text"}]},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Presentation","type":"text"}]},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"The storefront","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"The storefront takes customers from choosing a dish to placing an order, and adapts to them once signed in.","type":"text"}]},{"type":"image","attrs":{"alt":"Collections and the signed-in customer's “usual dishes”","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-02-collections-habituels-1792142632033.jpg","title":"Figure 10 — Collections and the signed-in customer's “usual dishes”","width":null,"height":null}},{"type":"image","attrs":{"alt":"Catalogue: most-ordered dishes, ratings, prices and monthly orders","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-03-catalogue-1792142635071.jpg","title":"Figure 11 — Catalogue: most-ordered dishes, ratings, prices and monthly orders","width":null,"height":null}},{"type":"image","attrs":{"alt":"Dish page: rating, reviews and favourites","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-04-fiche-plat-1792142638128.jpg","title":"Figure 12 — Dish page: rating, reviews and favourites","width":null,"height":null}},{"type":"image","attrs":{"alt":"Dish page: order panel — nothing is charged before payment is confirmed","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-05-commande-1792142643598.jpg","title":"Figure 13 — Dish page: order panel — nothing is charged before payment is confirmed","width":null,"height":null}},{"type":"image","attrs":{"alt":"Recipe published by the restaurant: preparation, cooking, servings, difficulty","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-06-recette-1792142645289.jpg","title":"Figure 14 — Recipe published by the restaurant: preparation, cooking, servings, difficulty","width":null,"height":null}},{"type":"image","attrs":{"alt":"Marketplace: nearby restaurants open now","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-07-place-de-marche-1792142648082.jpg","title":"Figure 15 — Marketplace: nearby restaurants open now","width":null,"height":null}},{"type":"image","attrs":{"alt":"Customer area: favourites across all restaurants","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-08-favoris-1792142650671.jpg","title":"Figure 16 — Customer area: favourites across all restaurants","width":null,"height":null}},{"type":"image","attrs":{"alt":"Customer area: dietary preferences (diets and allergens)","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/boutique-09-preferences-1792142653723.jpg","title":"Figure 17 — Customer area: dietary preferences (diets and allergens)","width":null,"height":null}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"The restaurant back office","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Each restaurant runs its business from its back office: today's service, catalogue, offers, opening hours and its shop window.","type":"text"}]},{"type":"image","attrs":{"alt":"Back office: today's activity and stock status","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-01-aujourdhui-1792142163956.jpg","title":"Figure 18 — Back office: today's activity and stock status","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office: dish catalogue, prices and stock","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-02-produits-1792142164832.jpg","title":"Figure 19 — Back office: dish catalogue, prices and stock","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office: offers, discounts and promo codes","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-03-offres-1792142167413.jpg","title":"Figure 20 — Back office: offers, discounts and promo codes","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office: opening hours, public holidays and closures","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-04-horaires-1792142170495.jpg","title":"Figure 21 — Back office: opening hours, public holidays and closures","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office: collections shown in the shop","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-05-collections-1792142173469.jpg","title":"Figure 22 — Back office: collections shown in the shop","width":null,"height":null}},{"type":"image","attrs":{"alt":"Back office: home page configuration with live preview","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/backoffice-06-parametrage-1792142176515.jpg","title":"Figure 23 — Back office: home page configuration with live preview","width":null,"height":null}},{"type":"heading","attrs":{"level":3,"textAlign":null},"content":[{"text":"The platform console","type":"text"}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"The console, reserved for administrators, runs the marketplace as a whole: activity, restaurant onboarding, business model, compliance and traceability.","type":"text"}]},{"type":"image","attrs":{"alt":"Console: dashboard — gross volume, commissions, recurring revenue","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-01-tableau-de-bord-1792141643699.jpg","title":"Figure 24 — Console: dashboard — gross volume, commissions, recurring revenue","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console: versioned subscription plans","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-02-formules-1792141646659.jpg","title":"Figure 25 — Console: versioned subscription plans","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console: the platform's versioned legal documents","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-03-documents-legaux-1792141649672.jpg","title":"Figure 26 — Console: the platform's versioned legal documents","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console: reference data shared by all restaurants","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-04-referentiels-1792141652727.jpg","title":"Figure 27 — Console: reference data shared by all restaurants","width":null,"height":null}},{"type":"image","attrs":{"alt":"Console: chained, verifiable audit log","src":"/api/media/projects/291cecb6-92e0-46d2-bb17-b30d009e9396/console-05-journal-audit-1792141655734.jpg","title":"Figure 28 — Console: chained, verifiable audit log","width":null,"height":null}},{"type":"heading","attrs":{"level":2,"textAlign":null},"content":[{"text":"Outcomes and next steps","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"From monolith to platform:","type":"text","marks":[{"type":"bold"}]},{"text":" one deployable application became 18 services, 4 BFFs and 3 front-ends, each delivered independently.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Reliable ordering:","type":"text","marks":[{"type":"bold"}]},{"text":" checkout runs through an order, payment and stock saga.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Security:","type":"text","marks":[{"type":"bold"}]},{"text":" the monolith's six flaws are fixed and verified.","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"New capabilities:","type":"text","marks":[{"type":"bold"}]},{"text":" multi-restaurant support, subscriptions, offers, platform console.","type":"text"}]}]}]},{"type":"paragraph","attrs":{"textAlign":null},"content":[{"text":"Next steps towards a professional product: ","type":"text"},{"text":"going live","type":"text","marks":[{"type":"bold"}]},{"text":" and shutting down the monolith, ","type":"text"},{"text":"real-time delivery tracking","type":"text","marks":[{"type":"bold"}]},{"text":" and the customer ","type":"text"},{"text":"mobile app","type":"text","marks":[{"type":"bold"}]},{"text":".","type":"text"}]}]},"stack":["Java","Spring Boot","Angular","TypeScript","Tailwind CSS","PostgreSQL","Kafka","Docker","Stripe","MinIO","Valkey","Caddy","OpenTelemetry","Grafana","Flutter","Testcontainers","Claude Code"]}],"images":[]},"locale":"fr","languageId":"7d4b6d33-3a51-45af-8734-feedebe45c89","fallbackLanguageId":"7d4b6d33-3a51-45af-8734-feedebe45c89"}]}]]}]}]]}]