help.axcms.netAxinom Logo
Save Save Chapter Send Feedback

AxCMS.net Deployment Alternatives

 

As described in the "Components" part of the "Basic Concepts" introduction, every AxCMS.net installation consists of four main components:

  • The Management System
  • The Live System
  • The Publish Service
  • The AxCMS.Service

AxCMS.net enables different deployment scenarios while empowering administrators to meet the requirements of the customer's IT environment.

The simplest configuration is based on a single web and database server:

Fig. 1 Deployment; all components on one server

Fig. 1 Deployment; all components on one server

In this case (single Windows server) you can configure the publishing process without using WebServices - this process is called InProcess publishing. It stores pages and documents directly into the Live System without requiring an overhead for HTTP-communication. At the same time, it assures the clear separation between the MS and the LS.

You might want to separate the MS from the LS for a number of reasons. Some sample scenarios could be:

  • You are hosting the MS in-house, but allow the LS, with high traffic, to be hosted on premise of a 3rd party host.
  • You are running both the MS and the LS in different security contexts (the LS is exposed to the Internet, the MS is only available inside a corporate network).
  • You are hosting the LS on a high-performance server (or server farm); the MS is not suffering from high traffic load.
  • You need a deeper integration of the MS into the IT-environment.

A typical deployment diagram for when the MS and the LS system are separate:

Fig. 2 Deployment on 2 servers: MS and LS are separated

Fig. 2 Deployment on two servers: MS and LS are separated

Because of the clear separation between the MS and the LS, and the fact that communication between the systems is restricted to HTTP(S) communication only, splitting the components between different servers is not an issue. As you can see, you will need two instances of AxCMS.Service: one serving the MS and one serving the LS.

In some cases you will run the database (SQL Server) separately from your Web Server (Internet Information Server, IIS). The reasons for this could be related to workload, security, your company's policies, or the availability of the hardware and/or software licenses.

The overall approach is shown below:

Fig. 3 Deployment on 4 servers: Databases are on dedicated servers, MS and LS are separated

Fig. 3 Deployment on 4 servers: Databases are installed on dedicated servers, MS and LS are separated

You can also mix the configurations, e.g. run the MS database and Web Server on the same hardware, and the LS database and Web Server on a different one. As your system grows, you can consider running the LS in a load balanced environment.

Review the links below for further information.