ZibiWorks
Meet the Company
Architecture Case Study
Current Platform Introduce Seams Evolve by Domain
ZibiWorks is a fictional company that designs, manufactures, sells, connects, and services robotic companion animals.
Rapid growth has left it with a large monolithic platform, a heavily shared database, an expanding set of third-party integrations, and an increasingly complex fleet of connected devices.
The Series
Section titled “The Series”A fictional company. Real architecture problems.
This site follows the decisions, tradeoffs, false starts, migrations, and operational realities of reshaping ZibiWorks’ platform for its next stage of growth. ZibiWorks is deliberately not a finished reference architecture. The value is in watching it evolve: why a decision was made, what it cost, what it broke, and what had to change later.
The Journey
Section titled “The Journey”- Starting Point
- Decisions
- Decomposition
- Integration
- Operations
- Future State
- 01What's Driving Change?Before choosing a modernization architecture, identify what actually needs to change. Learn how business pressures, technical friction, and emerging needs shape modernization priorities.
- 02Move It or Fix It First?Should you move an application to the cloud or modernize it first? This ZibiWorks installment separates what cloud migration solves from what modernization solves, and shows how timing, dependencies, and economics shape the decision.
- 03Rewrite vs. EvolveRewrite or evolve a legacy monolith? Explore modernization tradeoffs, migration risk, and how business deadlines shape architecture decisions.
- 04Boundaries and MeaningWhere should a monolith be split? ZibiWorks finds business boundaries using bounded contexts and ubiquitous language before extracting Fulfillment.
- 05The First SeamA business boundary says what to separate; a seam says where. How ZibiWorks finds a safe technical seam to begin extracting Fulfillment from its monolith.
- 06Domain or Utility?When does a supporting capability deserve its own boundary? ZibiWorks sorts business domains, utility domains, and shared packages, and decides where shipping integration belongs.
- 07Who Owns the Data?Establishing Fulfillment's data authority while preserving legacy compatibility and defining the requirements for a fallback that protects data integrity.
- 08Choosing the Compatibility StrategyHow current must a legacy compatibility projection be, and how should it be kept that way? ZibiWorks compares CDC, API polling, domain events, and a hybrid.
Explore by Topic
Section titled “Explore by Topic”ModernizationWhat to fix in the monolith, and in what order.ArchitectureDomain architecture, APIs, events, security, observability.IntegrationConnecting systems across boundaries as they split apart.DataOwnership, migration, and splitting a shared database.OperationsBCDR, reliability, deployment, and cost.Future StateSaaS evolution, multi-cloud, AI-assisted development.
Reference → ADRs, patterns, glossary, diagrams, and samples.