It is more that services allow more backward compatibility than direct DB changes, because you can also code additional logic to maintain that. Of course in a

It is more that services allow more backward compatibility than direct DB changes, because you can also code additional logic to maintain that. Of course in a narrow case where all apps that need the same DB need to be upgraded/fixed in lockstep, maybe you can get away by directly updating the database. But more than 2 teams, it will quickly be a nightmare of conflicting priorities across teams, amount deployment coordination required. "Oh you cannot change this schema right now because 3 other apps depend on it and they dont have time to make the necessary changes in their app to accommodate this right now, for the next 6 months"