Capital One has repeated that phrase to me so many times, it’s amazing.  The fact that I cancelled my Cap One card after they charged me 10 times the fees of any other card means that this phrase now has another meaning… what should NOT be in my wallet.

Applying that to architecture…

One cool thing about EA, we get to think about the future.  What capabilities are required by the company, in the future, in order to meet the needs of a vision, a business goal, a dream…  It’s fun.

So I’ll ask “what’s in your roadmap?”

A federated ESB?

A common information model?

Matrix or Cloud database management?

Business process execution engines?

Near-real time Business Intelligence?

B-to-B federated identity management?

What bit of esoteric infrastructure or wild-eyed darn-near impossible business requirement is creeping into your five year view? 

I’d love to know…

By Nick Malik

Former CIO and present Strategic Architect, Nick Malik is a Seattle based business and technology advisor with over 30 years of professional experience in management, systems, and technology. He is the co-author of the influential paper "Perspectives on Enterprise Architecture" with Dr. Brian Cameron that effectively defined modern Enterprise Architecture practices, and he is frequent speaker at public gatherings on Enterprise Architecture and related topics. He coauthored a book on Visual Storytelling with Martin Sykes and Mark West titled "Stories That Move Mountains".

2 thoughts on “What's in your wallet?”
  1. "esoteric infrastructure":

    Is an "operational data store" considered esoteric?

    Does that mythical stage exist between transactional data (OLTP/Business Events) and the bulky data warehouse?

    If you have thoughts on this one, I’d love to hear them.

Leave a Reply

Your email address will not be published. Required fields are marked *

three + 14 =

This site uses Akismet to reduce spam. Learn how your comment data is processed.