Building a Robust and Highly Scalable Distributed Architecture using VB.NET - Architecture Implemented
(Page 3 of 6 )
The following diagram (Fig 1) illustrates the architecture implemented in this scenario.

There exists a Stored Procedure (pAreaInsert) in the database. A Serviced Component (CDataAccess.vb in COM+ Services) acts as a DAL (Data Access Layer) between Remote Component and Database. The Business Component (CArea.vb) is designed using Remoting and a Windows Service (RemoteAccessAgent.vb) hosts the Remoting Component to make it available to different Remote clients.
The downloadable Visual Studio.NET 2003 solution with this article contains following projects built into it:
- DataAccessComponent – Serviced component acting as data access layer.
- ConsoleCOMPlusClient – To test Services Component.
- BusinessComponents – Remoting Component implementation.
- ConsoleRemoteServer – just to Host Remoting Component as server (without windows service).
- ConsoleRemoteClient – Just to test the Hosted Remoting Component Server with a Remote Client (without windows service).
- BusinessComponentService – Windows service hosting the Remote component.
- ConsoleServiceClient – To test the Remote component hosted by Windows service.
- Setup1 – A windows setup project to generate windows client installation MSI.
DON’T RUN THE ENTIRE SOLUTION. You can test every tier (or layer) individually with the respective Console client application. Consider the following:
- Use projects 1 and 2 to access DB through Data Access Component directly using console application.
- Use Projects 1, 3, 4 and 5 to access DB through Data Access Component from Remoting component using a Console Remoting Client hosted by Console Remote Server.
- Use Projects 1, 3, 6 and 7 to access DB through Data Access Component from Remoting component hosted by a Windows service using a Console Service Client (same as Remoting Client).
Next: How to Test COM Serviced Component >>
More Visual Basic.NET Articles
More By Jagadish Chaterjee