If you want to buy a new TV, would you even consider a 20-year old CRT TV? If you wanted a portable music player, would you buy a walkman? Of course not. The world has changed significantly since both of those pieces of technology were invented. Those old television sets were built for a world that didn’t include high definition video. The walkman was built for a world without digital music. Using either one these days severely limits your options and capabilities.
In the same way that old technology limits our abilities, your old applications limit your company’s abilities. In what ways might old applications limit your capabilities? To get a better idea, ask yourself this question: What has changed since your applications were built? For example, suppose your applications were built 20 years ago. In that time…
1. The web has changed: Over time, we’ve moved from individual networks to a networked world.
2. Programming methods have changed: Programming methodology has evolved from procedural-based to event-driven programming.
3. Application structure has changed: In the last 20 years, we’ve moved from large, monolithic applications, to an application structure built on atomization of function.
4. The database has changed: Databases used to only store data. These days, much of the logic previously included in the application can be moved down to the database level.
These 4 changes have dramatically altered application capabilities and structure. They give you more options, lead to greater productivity, and lower costs. How so? There’s too much to put all in one blog post, but you can read more in this free white paper entitled, “Crash course in modernization.” It outlines how these important changes affect your applications, why they make modernization necessary, and your current modernization options.
I hope you find it useful.