Stay or Modernise? – Considerations for Modernising Legacy Applications
Your functional requirements, your existing online presence and your existing infrastructure strongly influence your choice of mobile platform.
Read: [More]
Your functional requirements, your existing online presence and your existing infrastructure strongly influence your choice of mobile platform.
Companies that have traded for a number of years will probably have one or more legacy bespoke business software systems that have a ‘maintain or replace’ question mark hanging over them. Given the high rate of change in contemporary enterprise IT architectures, answering this question is not getting any easier. There are a number of well known factors at play when considering whether to maintain or replace an application. The most common of these are detailed in table 1 below.
Table 1 : Application Metrics, Ranks and Remedies
| Metric | Rank | Y/N | Remedy |
|---|---|---|---|
| Application is secure? | 1 | Rearchitect, Recode | |
| Certification/vendor support | 1 | Replatform, Rehost, Recode | |
| Functionally Fit? | 2 | Recode | |
| Technically Fit (performance\availability)? | 2 | Replatform, Rehost, Recode | |
| Delivers Competitive Advantage? | 2 | Recode | |
| Application Portfolio Integration? | 2 | Rearchitect, Recode | |
| Mulit-Device Availability (desktop\mobile)? | 2 | Rearchitect, Recode | |
| Low Support Cost (Costs /Staff/Skills)? | 2 | Rearchitect, Recode |
If you answer No to any of the rank 1 questions or answer Yes to a majority of the rank 2 questions your application is probably a candidate for some form of modernisation. Modernisation can take a number of forms including performance optimisation, re-platforming, re-hosting and recoding. The form of modernisation suitable in your instance will depend on the combination of metrics that affect you application. Remedies for poor metric scores are proposed above.
In the instance where applications score poorly in relation to Functional Fit and Mulit-Device Availability it is probable that some form of recoding will be required. The options here will include application translation (i.e. using software tools to automate the porting of the application for one platform to another) or application recoding. Careful consideration needs to be given to the supportability of ported applications due to bloating of the code base if considering automated porting over application recoding.
Recoding and rehosting of legacy applications provide a significant opportunity to reduce application support cost from a number perspectives: internal infrastructure costs are replaced with incremental subscription costs when migrating to the cloud. The high costs of maintaining legacy technologies and scarce resources are replaced with the lower costs associated with using current technologies (possibly open source) and technical skills that are more widely available.
Historically, it has been common that application modernisation projects have been undertaken from the perspective of minimising costs and risks. Application modernisation projects also afford the opportunity to deliver significant competitive advantage for the organisation. Given the investment involved, it is important that due consideration is given to maximising this advantage for all project stakeholders.
Your functional requirements, your existing online presence and your existing infrastructure strongly influence your choice of mobile platform.
In today's market, finding the correct person to fill contract Oracle positions is a major challenge for businesses. Finding a candidate with the required professional and technical skills to undertake a fixed-term, highly specialized and technical job is almost impossible.
If you are in the process of rolling out systems into new channels (e.g. a mobile presence), migrating toward a cloud-based deployment or integrating with a new partner, you should give consideration to how your systems are integrated. An effective integration infrastructure facilitates business agility, simplifies on premise and in-cloud integration and reduces operating costs.
Your functional requirements, your existing online presence and your existing infrastructure strongly influence your choice of mobile platform.
Streamlining the process of migrating from OWB to ODI.
Background: Many Oracle customers currently use the Oracle Warehouse Builder (OWB) product as part of their data warehouse environment. Oracle noted in an OWB Statement of Direction that the current release of OWB (11.2) is the terminal release of the product and that no future releases are envisages. Furthermore, future database releases beyond Oracle Database 12c Release 1 will not be certified with OWB 11.2. On this basis, OWB customers need to identify a strategy and approach to migrate from OWB.
Background: In my previous blog entry: http://www.metalogic.ie/news/9/46/Best-Practice-Code-Organisation-and-Management-for-Oracle-ADF-Applications/d,ML_V2_News_Detail I described some initial considerations when starting a new Oracle ADF project, particularly in relation to ADF modules structure. Another consideration, when starting new ADF projects is that of building the project. In this blog I would like to explain one possible way to approach the application build process.
Using the Oracle Advanced Analytics Database Option can introduce analytic capability into existing Oracle solutions, delivering significant benefits with minimal time, cost and effort.
Recent trends in business intelligence and analytics has seen a shift in interest
Most Oracle ADF project codebases require reorganisation during their lifetime. Getting the structure correct at project outset can save significant effort and pain in the longer term.
A questions that often arises in enterprise software development environments is one of "how do we track requirements, change requests and software bugs. Additionally, how do we track source code to requirements, change requests and software bugs and track issues to software releases? Finally, how do we track time and effort against issues".
There are a number of questions that commonly arise in relation to Oracle database licensing.