A shared infrastructure services approach can simplify application support, reduce the number of vendors, eliminate unnecessary hardware/software/maintenance, and reduce costs by 8%-23%, depending on scale. This assertion is based on research performed by the Wikibon community and discussed at the March 23rd Peer Incite Research Meeting.
The concept of an infrastructure services architecture was first presented to the Wikibon community by John Blackman. The model presented at today's Peer Incite was simplified, but the messages are similar. A key premise of the model is that the business requirement defines the service, not the infrastructure. The intersection of infrastructure class (e.g. server platform), protection level (e.g. RPO/RTO) and performance tier (or grade) will determine what is delivered, the SLA, and the cost to the business.
Frequently, such a model will cause friction within application groups and lines-of-business that have often become used to having the freedom to mix, match, and let infrastructure groups manage myriad hardware and software options. However by implementing a menu-based services approach, organizations can retire bespoke assets and maximize skill sets.
Practitioners should expect such a model can apply to 80% of an application portfolio, with 20% of applications requiring specialized infrastructure.
Action Item: One-off implementations and purpose-built application infrastructure should be the exception, not the norm. A services-oriented infrastructure approach emphasizes standardization, re-usability, tested configurations, and transparent pricing to the business. Organizations should initiate such an approach for the majority of applications and retire outdated processes that encourage a 'one of each' mindset.
Footnotes:
