Discussion Locked

Application or Database Server

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Read the first paragraph for Nostalgic reasons :-)

I remember the days of FoxPro programming; usually there would be one Executable and numerous .DBF files. The business rules were built in the executable. Managing or distribution of any businessrules meant making coding changes and rebuilding the exe. Gone were those days, the world moved on to a truer-client/server architecture. We would write Delphi, Power Builder, Visual Basic, Oracle Forms (and even FoxPro) programs that interacted with the RDBMS hosted on a set of servers. The business rules were split between the client and server (in terms of Integrity constraints, stored procedures and triggers). Then came the concept of Application Server. More business rules were moved from the client to these servers.

Some of the business rules hosted by the database servers were also moved to the application servers. I understand the Enterprises’ need for a common business rules layer, and I think the concept of Application Server having the business rules is just a hype. I do not see many reasons that would require moving the rules to application server from the database server. I know the application servers are designed to handle many more things, and I am not sure how many of them really are necessary and useful that the OS and Database can not handle. The makers of application servers have made us feel the OS and Database are not adequate.

Ofcourse stored procedures and triggers do not always conform to Object Oriented principles. However, making coding changes and deployment is easy. With application server, having one more layer just adds one more point of failure. To integrate their systems Enterprises now need more resources (hardware, software andpeople). There is an issue of performance with myriad layers.

So, what do you think, are the business rules better implemented on the database or application server.

1 reply

by sparkytd

Definetly the app server. Without any question, and I'll tell you why.

Your db should be left alone to handle only db related interations. The db should never cross over into the business rules, nor define any business rules. This, in turn, leads itself into a true 3 tier development environment. You have your db layer running exclusively on the db server, with a bridge to connect itself to the application logic....and the application logic should only contain logic relating to the application - ie. all business rules and presentment of those business rules. This again conforms to the tiered development environment. I think that if you implement the business rules on the db server or db tier for that matter(after all, it is possible to run a software package exclusively on one server), you have more of a tendency to break the tiered development cycle, which would cause major grief when you go to make changes. Imagine business rules implemented in the db tier, and you decide you need to move from a SQL server to Oracle. Now you have to go and modify your business rules as well as your db logic to implement Oracle. Whereas, if you go to change it with the business logic in the app server, you will not need to re-write your business rules as all db interaction is contained within the db server, providing an abstracted layer. All you may have to do is adjust your calls to the db, much less work and it'll also create a strong RDE for your developers.

My 2 cents

This discussion is closed to new replies.