Thursday 22 December 2016

Is JDE too slow in the mornings, perhaps it needs a wake up call?

Do you find that JD Edwards is a little tardy in the mornings or on weekends?  Would you like an innovative way to fix this?  I might have an idea for you!

We combine google analytics data on your ERP usage as well as AIS and LAMBDA in AWS to cache up the environment that you want to use.  Why do we use so many things to do this?  Because it’s completely dynamic and based upon demand.

As has been discussed before, we’ve configured Google analytics to record ERP usage and performance.  We extract the highly used applications:

A quick snippet shows the applications that are used most over the last month.

image

We have some LAMBDA code that loads this information dynamically and makes AIS calls to the relevant web server to those top applications. This ensures that they are cached and ready for use first thing in the morning.  What servers do you need for LAMBDA?  None!  by definition this is serverless compute.  So we are using no servers to troll your Active ERP usage and then ensure that these applications are ready for action.

I did not write any of this code, but my team of awesome innovation experts have done the hard yards for me!

Personally I think that this is some really innovative use of AWS and AIS to ensure that users have a consistent environment to work in.

You can then use google analytics to measure the page load times of the applications on Monday mornings to ensure that the performance is consistent.

No comments: