In today’s throwaway society we often assume that when something is a few years old we need to replace it with a new one. This is certainly the case for many technology items such as mobile phones and laptops where we replace them every few years with the latest technology. But in the case of large enterprise applications there is too much development time and effort invested to even think about replacement. Often the core business logic of the application is sound, but as time moves on improvements are needed to take advantage of new developments, to meet the current needs of a business.
So what do you do when your mission-critical enterprise applications need an update?
The question sounds like it is crying out for a nice long technical answer full of jargon and complicated diagrams.
But let’s first look at WHY you may need to update.
In our experience the main reason for considering the modernization or even migration of some of legacy applications is business enablement. Of course there are times when a technology is at end of life in a mission critical application that the business case for modernization is strongly technical but we find that the following drivers are equally likely to drive the need for such a project:
Not cool enough for Gen Y
Generation Y needs to be considered. (people born between 1981 and 2000), a generation that has never experienced green screens until they are thrust into the work force find it very difficult to adapt to what they see are archaic systems. Training becomes more difficult, time consuming and expensive and the attrition rate may well suffer. Also employees talking about how old the systems seem to be in any public forum is going to be damaging to your brand. The obvious and fairly quick alternative is one of the excellent re-rendering tools on the market. Not only can they make your systems looks new, connect well to the internet but they can also combine many applications in to a single seamless superset (known as a mash-up). Continue reading