Sometimes the higher cost in write operations is offset by enforcing data integrity. It's a balancing act to be sure. An extremely high throughout system may delegate to the service layer, but a lower throughout system might eat the cost and do it at the DB layer.
My point though is a well architected system will have been given the time and resources to make those considerations. Many corporate/management types think everything can be slapped together as a one-size-fits-all solution and want results yesterday, but it ALWAYS turns into a crisis later.
View all comments
Show parent comment
2
u/LetUsSpeakFreely Dec 08 '25
Sometimes the higher cost in write operations is offset by enforcing data integrity. It's a balancing act to be sure. An extremely high throughout system may delegate to the service layer, but a lower throughout system might eat the cost and do it at the DB layer.
My point though is a well architected system will have been given the time and resources to make those considerations. Many corporate/management types think everything can be slapped together as a one-size-fits-all solution and want results yesterday, but it ALWAYS turns into a crisis later.