PHP 7.3.14 Released

Voting

Please answer this simple SPAM challenge: zero plus four?
(Example: nine)

The Note You're Voting On

x12code at yahoo dot com
12 years ago
About offloading business logic to views and queries facilitated by the database engine, I seek to avoid this as much as possible, and only do so when such would drastically improve efficiency and user response time.

For instance, where I am there is database staff and application staff. Trying to do analysis on existent applications can easily become a snipe hunt.

The database should be kept discreet as much as possible from the application, such that any database or database provider can easily be substituted with a minimum of cognitive effort on the part of the one setting up a new database. If functionality has been offloaded to the database, additional testing is required to make sure triggers and views were done correctly, again, and that they work right.

Also, keeping all business logic with the application allows all functionality and documentation to be readable in one place, which is invaluable when doing subsequent analysis on an existing application. The worst thing is to have functionality scattered here and there.

Keeping everything with the application means one group of people is responsible, as in my case, application staff. Fewer requests go back and forth. Remember, anytime someone else is brought into the picture, such as asking a DBA to create a view or trigger for you, that DBA must take responsibility over his or her work, with whatever requirements, causing more bureaucracy and administrative complexity.

<< Back to user notes page

To Top 北京赛车pk开奖直播视频
北京快三 篮球指数即时指数 北京快中彩 雷速体育破解版 球探足球比分 即时比分直播 006足球直播网 韩国职业棒球比分直播 亚洲足球即时赔率 澳洲幸运5 足彩胜负彩 贵州快三 生肖时时彩 蓝球即时比分网 亿客隆彩票 7m体育篮球比分网