How to implement multi-tier architecture in our SQLite3 Framework
In software engineering, multi-tier architecture (often referred to as n-tier architecture) is a client–server architecture in which the presentation, the application processing, and the data management are logically separate processes. For example, an application that uses middleware to service data requests between a user and a database employs multi-tier architecture. The most widespread use of multi-tier architecture is the three-tier architecture.
Both ORM and RESTful aspects of our framework makes it easy to develop using such a three-tier architecture.
In our SQLite3 Open Source framework, for Delphi 7-2010, you can follow this
- Data Tier is either SQLite3 and/or an internal very fast in-memory database, most SQL queries are created on the fly;
- Logic Tier is performed by pure ORM aspect: you write Delphi classes which are mapped by the Data Tier into the database, and you can write your business logic in both Client or Server side, just by adding some events or methods to the classes;
If you need a RAD approach, it's perhaps not the right tool for you.
But if you like describing your application with classes, it's worth taking a look at it, and contributes to this open source project!
We can give you more details about each Tier/Layer in our forum.