How to Modernize Your IT?
How to Modernize Your IT?
Everyone wants a modern IT, but how do you do?
Join the DZone community and get the full member experience.Join For Free
To have modern IT is to have an IT that uses modern technologies, components, and architectures. This search for modernity must be carried out within a thoughtful framework, taking into account the expected return on investment, the constraints of obsolescence, and the need for business differentiation. Indeed, what is the point of modernizing an application that is little used and has little business value?
You may also like: Introduction to Integration Patterns
For us, the main lines of thought are first of all to offer a modern foundation, with good global governance of its IT, a modern integration architecture, to finally be able to manage its governance of technological watch as well as possible, and finally, of course, the monitoring of obsolescence.
Global Governance of IT
Good knowledge of one's IT is essential for the introduction of new technologies and new architecture patterns.
To deliver value as quickly as possible, it is essential to map your IT as closely as possible. Where are the data? Who is the master of it? What are the flows? What are the processes?
The Modernity of the Integration Architecture
A modern integration architecture makes it possible to isolate applications, but also to make data much more available. It must be understood that it is quite possible to use older applications in modern IT, via an adapted integration architecture.
Strong use of API Management as an essential and central component of exchanges, the implementation of a Data Hub with the use of integration components such as Change Data Capture, ETL, ESBs, make it possible to make available to all data and services without constraint for the backends.
Governance of the Technological Watch
There is no point in using a technology that has just come out because without feedback it is impossible to know if it is appropriate to use it. At the same time, we should not wait too long to adopt new technology at the risk of allowing obsolescence to take hold naturally and structurally.
This requires constant monitoring, and a quick assessment of the future relevance of new technology so that it can be adopted as soon as all guarantees are in place. It is, therefore, necessary to carry out POCs, organize publisher meetings, organize exchanges on REX in conjunction with the service companies referenced by you, go to seminars and trade fairs, and organize its monitoring on the Internet.
You can practice this approach internally, sharing and monitoring via an Architecture Lab, whose feedback can be shared inside your company.
Once the technologies have been identified, they must be added to the internal services catalog and promoted, via webinars for example.
Finally, we must also share this technology watch with the business lines as part of a full innovation management approach, to develop new use cases.
Obsolescence monitoring must be carried out on all applications, whether on editor solutions or "in-house" solutions. It is necessary to map applications and list the underlying components, to be able to identify applications that will end up without support, or that will use obsolete components and/or frameworks. It is then necessary to launch upgrade campaigns, after impact studies.
And you? What do you do to be sure to have always modern IT?
Opinions expressed by DZone contributors are their own.