Occasionally a battle erupts in our department between the application architects (AAs) and the data architects (DAs). For example, the AAs want to remove database referential integrity so that programming or data movement will be easier. We DAs attempt to convince them that this may be a good short-term plan but will be bad for the long-term integrity of the data, which should be at the forefront of our data design decisions. Once we are deadlocked in battle, upper management becomes involved to break the tie. More often than not, they side with the AAs. We think it’s because the managers understand application functionality much better than they understand data architecture. What steps can we take so that we will start winning more battles?
AAs vs. DAs
Posted in Roles and Responsibilities