RE: MVC Architecture and transactions

From: Takken, Cor

Keeping in mind that the multi tiered architectures allow for physically
disconnecting the database from the platform where the actual programs
are running,

On the other hand, commitment control starts to get really complex when you
talk about different databases on different machines. So in fact,
multi-tiered architectures actually make commitment control less attractive
in certain circumstances.

and that we normally want to develop systems which are
future-proof (so, keeping the impact of changes as low as possible) we
have to allow for this happening.

"Future-proofing" is a bad argument for adding unneeded complexity. If your
business has a requirement today, address it. If foresee a possible new
requirement in the future, consider it when you design, and be sure to
design in such a way that you can add the feature later, but don't add it
today.

One of the tenets of agile technology is to not add features you don't need,
and there's a lot of common sense behind that particular philosophy.

Just to be absolutely clear: I'm not arguing against commitment control.
There are situations where it certainly makes sense. I'm simply saying
that, like any technology, you carefully address the reasons why you're
using it and make an informed business decision.

Joe