Technical Tutorials : Microsoft Dynamics NAV – Architecture (Introduction)

As a start to the Microsoft Dynamics NAV Programming tutorial series we will discuss about the Microsoft Dynamics NAV 2013 architecture. Knowing the basic concepts of Microsoft Dynamics NAV architecture will be helpful during the programming. 

History of the Microsoft Dynamics NAV Architecture.
Versions before the Microsoft Dynamics NAV 2009 was build on a two-tire architecture and it is based on the true client/server distributed data solution. In this model of the Microsoft Dynamics NAV, data and the data manipulation layer is included on the server and application,presentation logic, and presentation layer is included on the client. 

In other word presentation layers is included in the classic client of the Microsoft Dynamics NAV. This means application logic in other word business logic and presentation layers which handle user interface are included in the client computer. 

Microsoft Dynamics NAV 5.0 architecture 

The two-tier architecture also puts the data and data manipulation layers (DML) on the server in the native database and SQL Server configurations. 

What is the new architecture of Microsoft Dynamics NAV ?
Microsoft Dynamics NAV is build on a three-tired architecture model that use three core components. This three-tire architecture was introduced with the Microsoft Dynamics NAV 2009. With this architecture, in which the data and data manipulation layers are put on their own servers, the application logic is put on its own server, and the presentation and presentation logic are put on the client. 

  • The client tire – This it the layer which handle the front end of the Microsoft Dynamics NAV. Every user interaction is handle by the client layer and  it is also called as “presentation logic layer”
  • Middle tire or Service tire – Middle-tier is a multithreaded tire which manages the business logic and all the communication in NAV. 
  • Data tire – As it name indicate this tier handle and provide data component. Microsoft SQL Server provide the data layer to Microsoft Dynamics NAV. 
The Three Tiers of the RoleTailored Architecture
The new three-tier architecture is multithreaded so that it can handle more than one process at a time. This architecture overcomes the intrinsic limitations of the two-tier architecture. 

Can we have several server instance? 
It is possible to have several Microsoft Dynamics NAV instances in same server and each of this server instances can be connected to ONE Microsoft Dynamics NAV database at a time. It is also possible to connect several Microsoft Dynamics NAV Server Instances to a one database. 

Please provide your feedback with a comment. 

Happy Coding!
Thank you and Regards,
Tharanga Chandrasekara

Click on a star to rate it!

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?


  1. great stuff thanks given such useful information.we are one of the leading Microsoft dynamics nav training institution in India with well experienced faculty

  2. Very interesting article. Microsoft dynamics NAV architecture is a really interesting topic 🙂

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.