You want to have each layer do only a small part of the application.
The data layer is closely tied to the database, and enforces referential integrity and does only inserts, updates, & deletes. The business logic layer enforces business rules ("to add a customer, you must have these values") and permissions ("to add a customer, you must have the add-customer permission flag"). The boundary layers aggregate information from various layers and presents the data in a format that the front-end layers (screen, web-service, import/export) can understand. The front-end layers do nothing but format the data.
Where people get in trouble is when they try and get each layer to do too much. The simpler the better, and the more scalable your application will be.
Chip H.
____________________________________________________________________ If you want to get the best response to a question, please read FAQ222-2244 first
Thanks Chip. What I am really looking for is a good example that I can learn from, either in a book or on the net. I know the basics of OO, but I'm no expert and would learn a lot by following through an example of a real life application using an n-tier architecture.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.