Writing software and creating software development teams. Mostly the people parts.

Principle I'm Referencing

ACID, a set of properties of database transactions.

One of my teams is building a business process-based experience. We’re building on an api that’s very data-model based and it’s created some unique challenges. One of my canonical rules is that there’s frequently a canonical rule. Some general-purpose knowledge that provides guidance if not a full-on framework to utilize.

Here, ACID guides us to develop using Atomicity and Consistency principles to provide rollbacks in case of failures as well as maintaining consistency with the existing business rules.