About the Application Object Server

The three-tier configuration (data server, an application server, and a client) uses a database to hold the data (tables), and a middle tier where the application objects, such as queries and classes, are executed. The user interface related application objects, such as the forms and reports, all run on the client computer. By using fat clients it is possible to let even objects such as queries, classes, and other application logic execute on the client. The fat client also features direct access to the database.

When you separate the application’s data from its other application objects, it is a lot easier to distribute upgraded versions of your application. You can distribute upgraded versions of forms, queries, classes, and reports which are based on the same set of underlying tables, thus the application’s data is not affected. Another benefit is that by splitting up the data (tables) from the other application objects, you can reduce the load on your network.

When separating application data and logic into different tiers, one can benefit from industry standard back-end products like Oracle DBMS and Microsoft SQL Server. It also makes it possible to tune the load on machinery and network to maximize throughput and reduce response time and scalability. By introducing a middle-tier, sharing objects and information becomes an effective tool to increase performance. Last but not least, the different tiers can work as a shield with respect to security.

The client/server application developer's dilemma lies in knowing how to split up the work between the different tiers. Microsoft Dynamics AX and the SQL databases that can be used together with it all have very powerful database engines. They all have powerful programming languages, and are capable of validating data and enforcing business rules.

Community Additions

Show: