Generally an Application comes with 3 parts.
- Presentation logic (PL)
- Business logic (BL)
- Data storage
Arranging 3 parts of application will provide 3 types of architectures.
- Single tier (or) Monolithic Architecture
- Two tier
- Three tier
2. Two tier architecture : When the requirement is sharing data by set of applications, the solution will be two tier architecture.
The business logic is repeated in each client system. It requires reusability and better maintanance. The solution is maintaining Business logic with database server in the form of stored subprogram. This is called 2(1/2) tier architecture.
When it comes to enterprise level it is not recommended to maintain business logic with database server for the following reasons.
- More burden on database, it will degrade performance of database.
- Each client system requires clientside software of database. The company should purchase more number of clientside licenses for database. This requires more financial investment.
- Providing database location to client system is not recommended in certain cases for security reason.
- When the organisation is moving from one database to another database, the maintanance will not be easier. The solution is three tier architecture.
- In traditional Visual Basic 6.0 , it supports 3-tier implementation with DCOM.
- In Visual Basic (DotNet), it is provided with Remoting and Web Services.
- Java supports 3-tier architecture with RMI.
In another article we will see about Remoting and WebServices in Vb.Net.