A property-tax assessment update must write both the assessed value…

Question

A property-tax assessment update must write both the assessed value and the related lien flag in one commit, and both fields always change on the same release cadence. What should the team do about service boundaries?

Accepted Answer

Keep the tightly cohesive transactional core in one deployable until the boundary naturally loosens — Some ledgers must flip two columns together—like stamping both pages of a dual-entry book. Forcing those pages into separate buildings just so you can call them “microservices” usually creates more pain than freedom.

Answer

Split them into two services immediately and invent a distributed transaction across the chatty pair

Answer

Put each write in a separate eventual-consistency saga even though they must succeed together

Answer

Expose both writes only through separate public APIs with no shared transactional boundary

A property-tax assessment update must write both the assessed value and the related lien flag in one commit, and both fields always change on the same release cadence. What should the team do about service boundaries?

Short Explanation

Full Explanation