Consolidation of Business and Database Logic
Depending on the human resources, some of our functions use an MTS component
to house as many routines as possible for a particular process function,
housing both business logic routines and database access routines. Other
functions isolate the business logic and database access in in separate MTS
component s so that the business layer object instances the data access
object. Data is most often marshaled as ADO Recordsets regardless as to the
"client" who made the call.. In either instance, the UI server (Domino
server) instances and call methods of the component containing the business
My question is: What would your recommendation be for consolidating or not
consolidating business logic and database access in a single MTS component.
Additionally, would you recommend dividing particular process function MTS
components into multiple smaller components to reduce .DLL size?
Top DevX Stories
Easy Web Services with SQL Server 2005 HTTP Endpoints
JavaOne 2005: Java Platform Roadmap Focuses on Ease of Development, Sun Focuses on the "Free" in F.O.S.S.
Wed Yourself to UML with the Power of Associations
Microsoft to Add AJAX Capabilities to ASP.NET
IBM's Cloudscape Versus MySQL