All articles

  1. Azure & Cloud

    What a slot swap promises, and what it abandons

    A deployment slot swap warms the new version, moves production traffic to it without dropping requests, and keeps the old version one swap away. It does not protect the work running on the old instances, stop timers and WebJobs running in both slots, carry the identity and some settings across, or undo on the way back what the new version wrote.

    ·12 min read

    Keep reading →
  2. Migrations

    A SharePoint cutover stops being reversible when the new farm accepts writes

    Keeping the old farm available preserves a fallback environment. It does not preserve changes accepted by the new one. A decision matrix and an offline counterexample separate routing recovery from data reconciliation.

    ·6 min read

    Keep reading →
  3. Development & automation

    A hybrid SharePoint integration needs more than a successful sign-in

    A Java or .NET API can authenticate a caller while the downstream SharePoint operation still has the wrong authority. Compare the identities, contracts and failure boundaries before choosing a gateway or extracting legacy functionality.

    ·6 min read

    Keep reading →
  4. Development & automation

    Writing to two systems is not a transaction

    An application that saves one change in two systems has two outcomes, and nothing commits them together. What Microsoft's architecture guidance says about why the copies drift apart, where a transaction across two systems does exist, and what makes the result recoverable: one record of the change, delivered at least once to a consumer that ignores repeats, and compensation for what cannot be derived.

    ·15 min read

    Keep reading →

Categories

Send us a message

or write to hello@ph7x.com

Contact