Development and Operations – DevOps
DevOps isn’t a tool or a product, it’s an operational approach that changes how organisations think about developing and deploying applications. The approach looks at infrastructure and software as a serviceable layer that can be fully automated and therefore made to be repeatable with expected end results. This cannot be done with process alone, people and tools are needed across the landscape to fully realise the potential. In terms of Microsoft Dynamics AX, AgileCadence are taking all the experience and knowledge from the DevOps movement and making it a reality within the AX ecosystem.
There are numerous configuration management tools that automate the configuration of compute instances and applications. They help applications stay operationally sound, while allowing change to occur in an automated fashion. At AgileCadence we focus on keeping your AX software working as desired without the drift seen in almost all implementations of AX and other software where the DevOps ideal has not been recognised. Not only can we cope with software changes across the subsystems and software, but we can also cope with internal configuration of the app itself. We believe that this is a watershed moment for AX ecosystem, if you agree then it’s time to speak to us.
Centralised logging is a must in any scalable environment, but it is vital to the health of a DevOps organisation. Centralised logging allows developers and systems engineers to search logs and create a more transparent picture of what is causing problems in the application stack, or where performance tuning may make a difference. But let’s take this a little further. What about centralised logging of the stack across all systems without boundaries, Public, Private or Hybrid cloud. What if this could be offered simply and effectively and using some of the best and proven domain knowledge with regards to Dynamics AX?
Source Code Management
Core to DevOps is automation. Developers have used Source Code Management (SCM) in some sort however using a SCM regularly may be new to some systems engineers, but all code must be checked into a SCM. Placing all automation, infrastructure, configuration, and application code into the same repository allows every component to run an application to reside in the same place. Ideally, all artefacts for running the application are in the same repository and versioned together as a single deployable artefact. This is a huge breakthrough for organisations and something that can change the way of thinking and acting long term. Imagine being able to deploy code to a known infrastructure, configured in the same way it was meant to be and tested as working, to all instances of AX.
Continuous Integration Tool
Build and deploy orchestration helps DevOps teams automate and create repeatable processes. Teams adopting the use of Continuous Integration (CI) tools find that they spend less time doing lower value tasks, freeing them up to focus on new feature creation and deeper automation in the deployment process. AgileCadence have experience with a number of core tools but also have created extremely durable, tried and tested processes and tools using PowerShell, we don’t just think it works, we know it works.