I was looking at Amazon’s new S3 Simple Storage Service this morning, and the final design principle caught my attention:
Simplicity: The system should be made as simple as possible (– but no simpler).
Words to architect by…
Archives for March 2006
LinuxWorld – OpenSolutions World – Boston April 4, 2006
I’m planning a day trip on Tuesday, April 4, to catch some sessions at the OpenSolutions World conference within a conference at LinuxWorld. The OpenSolutions conference covers some interesting topics higher up in the stack, with a fair amount of enterprise oriented sessions.
Sessions on my short list are:
The LAMP vs J2EE vs .Net Shootout – What Every Enterprise Developer Should Know
Leveraging Open Source to Build Web 2.0
SOA and Linux Reference Architecture: Open Source in the Enterprise
Open Source ERP & CRM – from oddity to mainstream
Amazon Mechanical Turk: A Web Services API for ‘Artificial Artificial Intelligence’
If you plan to attend and want to connect, shoot me an email: bmichelson at psgroup dot com
James McGovern’s EA 2.0
James McGovern, Enterprise Architect for The Hartford, and all around Enterprise IT Thought Leader, recently posted the characteristics of Enterprise Architecture 1.0 versus Enterprise Architecture 2.0:
1.0 2.0
Abstract Authority Community
Project Oriented Management Strong
Technical LeadershipComprehensive Documentation Working Software
Following a Plan Responding to Change
Governance Stewardship
Rationalization Innovation
Outsourcing Open Sourcing
NDA Declarative Living
Large Analyst Firms Small Analyst Firms
Management Leadership
ERP for IT Burndown
CMMi Agile Methods
Best Practices Practical Considerations
Reference Architectures Shared Vision
Time Accounting Functional Delivery Accounting
Buy vs. Build Buy vs. Build vs. Open
Project Oriented Service Oriented
Politics Diplomacy
Polarization Dialog
Buy-in Enlistment
Restrictions Rights
Cathedral Style Development Bazaar Style Development
Process People
This is a great list. I see a lot of synergy with my own thoughts on Business-Driven Architecture. In typical James fashion, he encourages the architect community to discuss and comment upon his list:
If others have insight into emergent behavior in this space, please do not hesitate to either leave a comment and/or respond from your own blog. We do not mature as a profession until we start having honest open conversations amongst each other…
With that, I offer a few additions:
EA 1.0 EA 2.0
Big Bang Incremental
Rigid Tolerant
Technology-Driven Business-Driven
And encourage readers to participate along with James, in advancing EA 2.0…
