Feeds

The Legacy Dilemma

Architecture giveth, vendors taketh away?

  • alert
  • submit to reddit

3 Big data security analytics techniques

In IT circles, the term ‘legacy’ is generally banded about as a kind of shorthand, to suggest that a system or application has reached a certain point in its existence where the only way is down. There is no concrete definition – well there is if you browse the 'net, but it tends to reflect the above (for example, “a system which has been superseded but which is still in use”). Which isn’t really much help in system planning.

So, other than such bland generalisations, is it possible to characterise legacy and if so, how? To resolve this issue, who better to ask than the Reg readership. In fact, the answers we received to our poll last week were pretty telling. As we can see from Figure 1, the number one characteristic that could quickly turn mainstream into has-been was the question of vendor support. Hmm, does this suggest that IT environments would be better able to withstand the vagaries of change if only vendors allowed them? Well, yes, actually it does.

Fig1

While none of the other characteristics were seen as irrelevant – in other words, they all have a part to play – it is worth calling out the lack-of-system-flexibility driver, which appears bottom of the list. Far more important than the flexibility of individual systems, and indeed ranking equally with the loss of skills over time, is the issue of integration between systems. This is fascinating stuff, if for no other reason than it validates the need to consider the IT environment as a whole, over and above treating individual systems.

This priority is reflected when we consider what the 303 poll respondents considered as most important to protect against systems becoming legacy before their time. As we can see from Figure 2, having good architecture and design in mind is the number 1 criterion. Unfortunately, we know from other studies that this isn’t always treated as a high priority early in the design stage. However, at least it’s useful to know – findings such as these are a useful counter to anybody who suggesting they’ll worry about such things later.

Fig2

Of course, architecture can’t protect against individual vendors withdrawing support. However, what we can do is extrapolate these findings to the IT environment as a whole. If integration is a key issue, and well-architected systems a key protection, it is not hard to see how such questions as open standards and interoperability become important when ensuring the future-safety of our systems and applications. Built-to-last IT is an oxymoron and nobody can prevent change from happening, but at least we can make savvy design decisions early on, which can extend the life of both individual systems and the whole infrastructure.

SANS - Survey on application security programs

More from The Register

next story
Android engineer: We DIDN'T copy Apple OR follow Samsung's orders
Veep testifies for Samsung during Apple patent trial
This time it's 'Personal': new Office 365 sub covers just two devices
Redmond also brings Office into Google's back yard
Batten down the hatches, Ubuntu 14.04 LTS due in TWO DAYS
Admins dab straining server brows in advance of Trusty Tahr's long-term support landing
Microsoft lobs pre-release Windows Phone 8.1 at devs who dare
App makers can load it before anyone else, but if they do they're stuck with it
Half of Twitter's 'active users' are SILENT STALKERS
Nearly 50% have NEVER tweeted a word
Internet-of-stuff startup dumps NoSQL for ... SQL?
NoSQL taste great at first but lacks proper nutrients, says startup cloud whiz
Windows 8.1, which you probably haven't upgraded to yet, ALREADY OBSOLETE
Pre-Update versions of new Windows version will no longer support patches
Microsoft TIER SMEAR changes app prices whether devs ask or not
Some go up, some go down, Redmond goes silent
Red Hat to ship RHEL 7 release candidate with a taste of container tech
Grab 'near-final' version of next Enterprise Linux next week
Ditch the sync, paddle in the Streem: Upstart offers syncless sharing
Upload, delete and carry on sharing afterwards?
prev story

Whitepapers

Designing a defence for mobile apps
In this whitepaper learn the various considerations for defending mobile applications; from the mobile application architecture itself to the myriad testing technologies needed to properly assess mobile applications risk.
3 Big data security analytics techniques
Applying these Big Data security analytics techniques can help you make your business safer by detecting attacks early, before significant damage is done.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Securing web applications made simple and scalable
In this whitepaper learn how automated security testing can provide a simple and scalable way to protect your web applications.