Hi there. I have long been an advocate of infrastructure patterns (or blueprints). They have been around for a while and covered by a range of well known authors, but funny enough I struggle to find technical architects that talk to them, both technically and with the client.
The infrastructure blueprints provide the high level implementation framework for a solution on which vendor software is applied [and the patterns possibly altered]. The framework can state minimums across application service tiers, i.e. a class one application may using pattern X and storage pattern Y in order to achieve the required availability; and form the basis of enterprise standards on which specific vendor software platforms (further standards) apply.
The patterns can also provide a road map for change, allowing complex technical implementations to be boxed as logical concepts whose change over time can be articulated with the business and their respective clients. As with any change, infrastructure and software pattern changes also drives capability maturity - the possible need to invest in skills to sustain the stability and benefits of the pattern in production.
The presentation is a little rushed; but not too disorganised :) comments welcome.
http://www.chriskempster.com/data/Technical%20Infrastructure%20Patterns.ppt
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment