Microsoft Dynamics AX – Public, Private or Hybrid, it’s your choice
The team at AgileCadence have been working with Microsoft Dynamics AX systems since version 3 of AX. Once thing has been extremely apparent over the years and this is the staggering growth and complexity increase of the solution. However as with all products and technology experience cannot be learnt and we have more experience than most.
We know use that experience to size and manage some of the largest AX implementations in the world. Either working directly with the end customer or via the partner.
The exciting piece for us at the moment is the sheer possibilities that are opening up for organisations that adopt AX as their principle line of business application. Linking all of this with the offering of ALM and DevOps experience AgileCadence possesses makes us quite a force in the technical space of AX.
If you have any queries or concerns over your Public Cloud decision, please contact our team who will step you though the decision making process.
Agility Designing for agility and the demands of the organisation, especially on global deployments is key to success. We know this, because we live in this world.
Cadence – project heartbeat Keeping agility and application heartbeat in mind allow the infrastructure design to be looked at in a different way. Projects scale as they evolve, design this in upfront and overall reduce cost.
Baked in Monitoring, Configuration and Infrastructure as Code
When using AgileCadence, the question over how a system should be built is very relevant as we have an absolute answer and a fully implementable answer no matter what systems you are running. The team have been working to develop solid templated deployment and infrastructure guidelines and structures so that all of customers can gain best of breed implementations that just work, and that will pass muster when being interrogated by the Microsoft Premier Field Support consultants.
From the very first server deployed to the last, all systems are monitored from the first heartbeat they make. We take performance extremely seriously and spent time building an entire suite of monitoring and metrics that just keeps getting bigger and better.
Configuration Drift .. Maybe Not.
With all implementations of hardware and software, it is likely that at some point you will experience configuration drift of some description. This may even happen from the moment a server is delivered from the operations team to the project team.
Due to the way we approach our implantations, this should never be an issue again. We make sure that any new system is implemented as a templated node. We know what it should look like and we know when it changes, even better we can make the systems auto manage.
Imagine that? An AOS server becomes uninstalled by a junior administrator, but the server knows what it should look like and simple reapplies its designed software. This is what we do, we already have this and we already use this.