Domain invariant

An account balance never below zero unless an overdraft exists. A vehicle never rented to two people over the same hours. An invoice total always equal to the sum of its lines. These are not validations, they are properties of the business, and the difference is where they are enforced.

Put a rule in the application and it holds for the paths that go through that application. Then an import script runs, an admin edits a row, a second service is written by a different team, and the rule is silently no longer true — for a subset of rows nobody can identify afterwards. Put it in the database as a constraint and it holds for every writer that has ever existed and every one that will.

This practice sells that as the invariant on its architecture work: the domain model is the product. Not the interface, not the framework, not the stack — the set of statements the data is guaranteed to satisfy, because everything else is replaceable and that is not.

Enforcing it in the application layer only

The rule is written once, in the service that owns the feature, and holds until the second writer appears — which is always. By the time the violation is noticed the invalid rows are months old, mixed with valid ones, and nobody can say which state was correct. Write it as a constraint where the data lives; the application then cannot be the reason it is broken.

A definition sits still. This does not.

The term is a reading taken at a point in a sequence that is already running. These are the sequences, with the place each of them jams.

From something breaking to somebody confirming it works

An outage, from the moment the system stopped being correct to the moment a person has checked that it is correct again — including the parts that happen before anybody has touched a keyboard. 6 steps, monitoring whether the site is up is the arrangement that fails while looking reasonable.

Here is the number, and here is the page it came off.

A definition proves nothing. These are the places on this site where this quantity was actually computed, with the period and whose figure it is stated beside each one.

Somebody is accountable for this number.

A definition is free. Being answerable for the figure it produces is the part that is bought, and this term is a working part of the engagements below.

Platform and transactional architecture

The domain model is the product. Everything above it is an interface to it.

---

Anti-crisis engineering and recovery

Stabilise before you improve. A system under stress cannot absorb a redesign.

---

Custom software development and AI engineering for Dubai

A probabilistic component is only safe inside a deterministic boundary.

Transaction

A change that either happens completely or does not happen at all — and the argument is always about where it ends.

---

Consistency

Whether two people looking at the system at the same moment see the same thing — and how long “eventually” is allowed to be.

---

Data reconstruction

Rebuilding what the system knew from whatever survived it — the discipline that exists because the copy you were counting on is the thing that failed.

---

Migration

Moving data from one shape to another while the business keeps running — and the risk is never the data, it is the interval where two shapes are both live.

All ninety-six termsWhat this is regulated by in the UAE

Is this one right in your own numbers?

The definitions are the easy part. Whether the figure on your dashboard was computed this way is a different question, and usually the more expensive one.