I am often asked the question, what is Industry Architecture and why should I care? Well in very simple terms industry architecture is a way in which general technology architecture concepts are translated or applied to a specific industry to give that architecture the proper context. Alone technology is useless, it is just bits flowing over the wire. However with a business purpose it can provide value. Value can be tricky to define, it really depends on the goal you are trying to achieve, but for the sake of argument let’s say cost. The nice thing about industry architecture is that it can tie the concepts apply them to something tangible.
I am sure you have hearing a great deal about the new buzz acronyms such as SOA, ESB, IdM, CCF, etc. So the question is, how does that relate to an industry such as financial services? Lots of concepts right, but at the end of the day us architects want to see what is the value of let’s say SOA and how can I re-architect / augment / create new systems. Each industry is different with different business drivers and forces. Thus, we want to make sure the architectures we discuss are relevant to your business needs.
In future blog postings and in the publication of whitepapers in the MSDN architecture center you will see me address these issues to make these concepts relevant to you in the financial services industry.
Comments