Interview of Julien Topcu and Josian Chevalier
summary
Model mosis describes an iterative way to find microservice boundaries by observing runtime behavior and tolerating blurry responsibilities until evidence supports a split. It introduces model tension as the signal when one model tries to solve orthogonal problems, promotes evolving a modular monolith first, and names a lightweight intermediate the spark model. Changes happen over months with feature-driven experiments and production telemetry; no reliable automated extractor exists yet, only heuristic hints and possible future LLM-assisted analysis.
AI-written summary · about
related talks
46mModel Mitosis: Stop making the wrong choice between microservices and monolith
50mModel Mitosis: a dynamic pattern to deal with model tensions
46mFrom Chaos to Cohesion: Building Modular Monoliths in the Real World
50mModel Mitosis: No More Confusing Microservices and the Monolith
47mThe Joy of Multiple Models
49mMitosis Pattern
51mModularization: Foundation of Microservices and Monoliths
39mConsidering Migrating a Monolith to Microservices?