Nowadays many companies are thinking of migrating from previous versions of Dynamics AX to Dynamics 365 F&O, while a large number of companies in Russia are considering the on-premise implementation of this deployment, excluding the cloud option for various reasons.
We would like to share our experience in organizing development and testing environment for on-premise deployment in one of the current projects.
In standard Microsoft practice, the environment with on-premise deployment looks like this:
Developer, UAT (User Accepting Testing) and Production environments are deployed on the client’s local servers, while the test environment is deployed in the Azure cloud. This “long” scheme looks extremely suboptimal to use if a customer wants to save time, because the testing speed of it is low and rolling changes might take hours. In addition, the Customer has to pay for an Azure subscription.
The “long” scheme means that in order to deploy the update package, it will be necessary to re-deploy the entire server cluster on which this solution will be deployed, which takes much more time than the standard scheme for updating source files to one-box servers.
I-neti specialists suggested the implementation of a testing environment in the one-box format, in which the testing environment was also deployed on the client’s servers. This change made it possible to reduce the down-time of the test machine from 2 hours to 30 minutes, also if there is no need to synchronize the database during testing, the speed of testing changes was reduced to 8 minutes.
The main difficulty in this case is the need to duplicate all the functions that were previously standardly implemented in Azure “on the ground” in the absence of appropriate documentation. I-neti specialists have already made this path and are ready to help anyone who faces this problem in the deployment of development and testing environments.
Leave a Reply
You must be logged in to post a comment.