.comment-link {margin-left:.6em;}

Sam Lowe's blog on Enterprise IT

Tuesday, August 01, 2006

Dare I mention the word 'Applistructure' ...

I'm not sure who ever came up with the word 'applistructure', but I think it may just be one of the worst IT jargon words ever created. I have never been able to mention it to colleagues or clients without at least raising a smirk, or more likely inducing outright ridicule.

But actually, tempted as I have always been to disregard it as some believe we should, I do actually think the concept behind the silly word is rather important. In particular, for enterprise IT departments, I believe it represents something they should be thinking very closely about - in that it represents a significant change in the capabilities, divisions, skills and focus they need moving forward.

The idea is that 'applistructure' is the blurring of the line between enterprise applications and software infrastructure, in that, rather than specific silos of applications sitting on top of the shared software and hardware infrastructures, the enterprise applications themselves become part of the shared capabilities or resources which together are almost akin to infrastructures, at a higher level. This is to say that the application components (e.g. ERP modules, CRM modules, SCM modules etc) 'join up' with the software infrastructure that underpins them (e.g. app servers, integration buses, data management hubs, portal platforms etc) to form a higher level infrastructure that businesses can exploit, share and reuse.

Before your natural cynicism causes you to see red, let me explain why I think this is important.

Traditionally the lines between the functional people and the technology people in IT have been fairly firm, particularly in the packaged applications space. Both Oracle and SAP for example have very distinct teams, often with totally separate structures, both in their clients, but actually also within the software companies themselves. Although some separation is necessary for specialisation, the chasm that tended to emerge between the two sides (I believe) caused real quantitative and qualitative issues.

I believe that the 'reunification' of functional and technical IT viewpoint (whether you call it 'applistructure' or something else) is not a bad thing. For some IT departments, it will help move them away from purely obsessing about technology, and onto the business value from the architectural combination of the two. And for others, it helps force the functional IT people to not ignore the technology, and hopefully therefore to not carry on creating solutions in isolation of (or in spite of) the silo'd, duplicated or deprecated technology involved.

Of course this is closely related to the concept of SOA. As such, 'applistructure' implies that your SOA technology platforms need to managed and designed on the terms of your applications and data . No more separation considering interfacing as being separate from applications. In SOA you need a common unified and mutually-informed approach to applications, integration, data management, user interface etc. The decoupling requires this.

The concept of 'applistructure' also helps combat the plague of pseudo-value that has come into being recently, where software infrastructure platforms try and claim value propositions of applications they support. Quite frankly I've often in the past got quite irritated when software infrastructure vendors pitch their platform technology as directly providing business benefit even though it is not a solution. You know the kind that claims "our competitive differentiator is business agility" when all their technology does is provide a means to move data with less mouse clicks. I've always found this bizarre, as though the company that makes the tyres for my car would claim that their competitive differentiator is my timeliness for meetings, when what their product really does is at most allow me to go round corners slightly faster. Of course, it's not the tool, it's how its used with regard to specific solutions that is what drives business value. And by bundling up both solution-specifics and non-specific software under a common reusable architecture, the concept has far more leverage that the disjointed combination of applications and the various types of middleware did before.

So of course, one man's infrastructure is another man's application. But moving the average perception of what the platform is up, and moving the average level of concentration towards application of these higher levels of platform, may well be a very healthy exercise. Even if the word is still stupid...

Technorati Tags:

3 Comments:

  • Good posting. Good ideas. However,
    perhaps we should start a petition to nullify the 'Applistructure' term?

    Just kidding. Let's at least wait to see if SOA 2.0 can be successfully term-inated.

    By Anonymous Stephen Anthony, at 5:07 am  

  • Yes but unlike SOA 2.0 which clearly was opportunistic self-promotion/mis-direction (yes, I signed up as well), I believe we probably could do with a name/brand for this. Especially given that SOA is so overloaded.

    It just needs to be somehting that isn't so cringe-inducing.

    So maybe more replace than kill this time ...?

    By Blogger Sam Lowe, at 6:31 pm  

  • I quite like Business Process Platfrom which is a Gartner word that SAP have adopted. Prior to this I thought of Services and Rule Engine (SRE). I definately think that the name should show that the whole point is BUSINESS and not an IWF.

    Do you angry ?

    By Blogger Owen Pettiford, at 8:52 pm  

Post a Comment


via Haloscan

<< Home