Skip to content

Explore by Topic

Browse the ZibiWorks architecture by subject rather than story order. An installment may appear under more than one topic when it contributes meaningfully to multiple architectural concerns. Every entry links to the same canonical installment; only the grouping and summary differ.

Modernization

How ZibiWorks decides what to change and how far to go. These installments work through assessing a grown platform, separating migration from modernization, choosing between rewrite and evolution, and finding where a monolith can safely come apart.

  • Installment 01What's Driving Change?

    Start here: find where the current platform is limiting the business and which constraints actually deserve intervention, before choosing any architecture.

  • Installment 02Move It or Fix It First?

    Before deciding how to migrate, determine what genuinely needs to change and separate migration concerns from modernization concerns.

  • Installment 03Rewrite vs. Evolve

    Replace the monolith or evolve it? A decision record weighing the two transition strategies and why ZibiWorks chooses evolution.

  • Installment 04Boundaries and Meaning

    Before cutting the monolith, ZibiWorks looks for the business boundaries: where the language, the responsibilities, and the ownership genuinely change.

  • Installment 05The First Seam

    The first Strangler Fig cut around Fulfillment. How ZibiWorks evaluates where to place a seam so the transition stays incremental, reversible, and contained to one point.

  • Installment 06Domain or Utility?

    Where should shipping integration live? Choosing a Shipping Integration utility domain over embedding partner logic in Fulfillment.

  • Installment 07Who Owns the Data?

    Extraction is not finished when the code moves. Establishing data authority for Fulfillment while the monolith keeps running, and deciding what a fallback can and cannot promise.

  • Installment 08Choosing the Compatibility Strategy

    Choosing how a temporary compatibility projection is kept current during an extraction, and what would change the choice for a different organization.

Architecture

The shape of the system as responsibility moves out of the monolith: domain boundaries, seams, ownership, and the APIs and events that connect the pieces once they separate.

  • Installment 03Rewrite vs. Evolve

    The target architecture is largely independent of the migration strategy. This installment separates the destination from how you get there.

  • Installment 04Boundaries and Meaning

    The same business term can mean different things in different contexts. Those differences in meaning are a strong signal of where the real boundaries between domains actually lie.

  • Installment 05The First Seam

    A boundary says what to separate; a seam says where you can separate it safely. What makes a seam good is that it expresses business intent rather than legacy implementation mechanics.

  • Installment 06Domain or Utility?

    Reuse tells us little about where a boundary belongs. Telling business domains, utility domains, and shared packages apart, and deciding what to share without recreating coupling.

Data

Ownership, migration, and consistency when a shared database has to be pulled apart, including who becomes the source of truth and how data moves without breaking the systems that depend on it.

  • Installment 07Who Owns the Data?

    Who owns Fulfillment's data once the service is extracted? Separating location, ownership, and access, migrating open work, and giving the monolith a compatibility projection it can read but not write. Includes a legacy dependency matrix and a fallback decision matrix.

  • Installment 08Choosing the Compatibility Strategy

    Freshness, completeness, and recoverability are different requirements. Weighing CDC, API polling, domain events, and a hybrid for keeping the legacy compatibility projection current, and who is responsible for business meaning.

Operations

Where the platform runs and how it stays reliable and affordable: hosting and infrastructure lifecycle, deployment, reliability, business continuity, and cost as the architecture changes.

  • Installment 02Move It or Fix It First?

    Moving the existing platform introduces operational questions about production risk, sequencing, and what should be carried unchanged into the target environment.