.
Tue 25 Apr 2006SOA Governance and the Warren Buffett PrinciplePosted by Miko Matsumura under Uncategorized , SOA Blueprints , SOA Registries and Repositories , SOA Thoughts
No Comments
Warren Buffet, the second richest man on earth has a lot to say about SOA Governance. Lets have a look:“The key to investing is not assessing how much an industry is going to affect society, or how much it will grow, but rather determining the competitive advantage of any given company and, above all, the durability of that advantage.” - July 1999 at Herb Allen’s Sun Valley, Idaho RetreatThis quote speaks to one of the most important ideas in SOA–unlike the Nick Carr IT as commodity view of the world, SOA enables externalities such as competition, regulation, customer preferences and the fastest changing aspects of the business environment to be modeled as agile metadata process artifacts or as declarative policies or contracts. This means that the components underneath the service inter

.
Tue 25 Apr 2006Some Definitions for SOA GovernancePosted by Miko Matsumura under Uncategorized , SOA Blueprints , SOA Registries and Repositories , SOA Thoughts
1 Comment
So SOA Governance—I’m sure you’re seeing lots of announcements regarding this from an ever increasing motley crew of providers. These are all pieces of a larger puzzle.There is some significant confusion among end users about this vital topic. Gartner says that the top reason for failure in post-pilot SOA projects in 2006 will be a lack of governance mechanism—but with all the vendor buzz and confusion, there’s a need for clarification on this essential topic. Hopefully this guide will help.What is SOA Governance?It’s the creation, communication, enforcement, maintenance and adaptation of policies across the SOA lifecycle of design time, run time and change time.Why is SOA Governance important?It’s a poorly kept secret that SOA has too many moving parts. This means that without mechanisms of control a

.
Mon 1 May 200615 leading SOA Companies announce SOA LinkPosted by Miko Matsumura under SOA Blueprints , SOA Registries and Repositories , SOA Products , SOA Thoughts
No Comments
Fifteen founding members of SOA Link include AmberPoint, Composite Software, Forum Systems, Infravio, Intalio, IONA, JBoss, Layer 7 Technologies, LogicBlaze, NetIQ, ParaSoft, Reactivity, SOA Software, SymphonySoft, and webMethods.

.

.
Wed 17 May 2006InfoQ a major advance for SOA CommunityPosted by Miko Matsumura under SOA Blueprints , SOA Thoughts
No Comments
I wanted to post about an exciting new service called InfoQInfoQWhich is an AJAX driven next generation community online for tracking change and innovation in the IT industry. This is a very powerful resource!Have fun on this site… It should be a really powerful engine for the IT community to keep pace with what’s happening out there… I have joined as an SOA Editor for InfoQ and think that this site will be a huge resource for anyone involved in enterprise technology!Miko

.

.
Fri 2 Jun 2006CodeMonkeyPosted by Miko Matsumura under SOA Thoughts
No Comments
http://www.jonathancoulton.com/mp3/Code%20Monkey.mp3Very good lyrics, music is kind of predictable. Worth listening to (link is to an MP3)

Thu 18 May 2006apt-get JavaPosted by Miko Matsumura under Uncategorized
No Comments
Quick not-really-SOA type post (it’s about Java / Linux)Two reactions to Simon’s post about apt-get Java package and changes to distro friendly licensing for Java Runtime.1) a very well deserved thanks and congratulations to Simon and his team on this, it was neccesary and a positive step both the license changes and the packaging.Making Java a first class package on Linux was something I was working on in 1998, as you can see from my java-linux posting in Feb of 1998 updating the community on Sun’s head-in-the-butt philosophy around Java/Linux at the time.So I cant help but to have as a reaction:2) What the hell took so long?My second co

.
Thu 6 Jul 2006Why a WSDL isnt a ContractPosted by Miko Matsumura under SOA Thoughts
No Comments
Recently the Semantic Annotations for WSDL working group at the W3C announced the First Public Working Draft of Semantic Annotations for WSDL. It has a very promising name. the WSDL document has been referred to by many as the “Contract” in SOA. This is true, but it’s really a contract that defines very little–because in business terms a contract establishes expectations, responsibilites, outcomes and in some cases consequences. And when I say expectations, contracts are very explicit when it comes to who is responsible to whom and what they will get.When I read about adding semantic annotations to WSDL, I first thought–hmm that’s a good idea. But in looking at the specification, I can see that it’s a wonderful answer to some of the problems of data integration in web services. But it’s not really what I was looking for.You see, the reason why I am interested in contracts is

.
Tue 25 Jul 2006HP Acquires Mercury Interactive– SOA implications including SystinetPosted by Miko Matsumura under SOA Registries and Repositories , SOA Thoughts
3] Comments
This is a big move for HP. The part that is of interest from the SOA perspective is the Systinet division of Mercury.So typically in software there have been two kinds of companies–central control oriented and distributed agility oriented. Central control oriented companies include CA, HP, Mercury, BMC and the Tivoli division of IBM. They tend to occupy a space in “the cloud” and deliver visibility by watching things happening in the network. On the flip side there are companies focused on agility. These tend to be application platform companies such as Microsoft, BEA, SAP, Oracle, and others. They tend to exist on “servers” and deliver business functionality. This acquisition further pushes the Systinet Governance functionality into “the cloud” and into the hands of centrally located control types

.
SOA Blueprints, Best Practices, Patterns and Attitude
Wed 23 Aug 2006SOA 12 step programPosted by Miko Matsumura under SOA Products , SOA Thoughts
No Comments
this comment was posted on Dave Chappell’s ZDNet posting called 10-step program. Reprinted here on SoaCenter for your amusement.I sometimes think that Enterprises dont need an SOA 10-step program, they need a 12 step program.http://en.wikipedia.org/wiki/Twelve-step_program1)We admitted we were powerless over inflexible IT systems—that our lives had become unmanageable. “Hi my name is Brad and I’m a tighly coupled systems addict…”2)Came to believe that a power greater than ourselves could restore us to sanity. I know… IBM!3) Made a decision to turn our will and our lives over to the care of God as we understood Him.Don’t worry, IBM Global Services will take care of us4) Made a searching and fearless moral inventory of ourselves. I dun wrong, I created redundant services in application silos boo hoo =(5) Admit

.

Wed 30 Aug 2006DIE SOA REUSE DIE!Posted by Miko Matsumura under SOA Registries and Repositories , SOA Thoughts
2] Comments
This was posted in response to the article Pouring Cold Water on SOA Reuse.So Charles Stack from Flashline BEA talks about the Three “R”s of SOA
which he says are Reuse Reduction and Remix.Kind of like the ecological mantra “Reduce Reuse Recycle”.Unforunately, Reuse in SOA is Crap.One of the most blindingly obvious things about Enterprise software is that there is a TON of redundancy to it. There’s redundancy of hardware, redundancy of function, redundancy of software, of services etc.So the idea of SOA magically offering you “reuse and reduction” is a joke. Why?Because much of the redundancy is there for a reason. Some of it is there for legitimate reasons, and some of it is there for pragmatic, but perhaps sub-optimal reasons like hoarding, greed, paranoia, lack of faith, resistance and generally acting like a recalcitrant bastard.For

.
Fri 1 Sep 2006RegozitoryPosted by Miko Matsumura under SOA Registries and Repositories , SOA Products , SOA Thoughts
No Comments
In response to Todd Biske’s use of the word “Reppistry” to describe an SOA Registry Repository in the following blog post:So much metadata, so little timeby ZDNet’s Joe McKendrick — Registry and repository are hot commodities in SOA, but where is it all leading us?Tom Critser of Infravio coined the term “Regozitory” to speak of Registry and Repository quite a few years ago! So he deserves credit for that one.Just to be clear, Registry in SOA has become pretty synonymous with “implements UDDI”. Now I’ve seen other registries including Microsoft Word, LDAP, JINI Lookup, the “water cooler”/word-of-mouth service discovery etc etc.But “Repository” is a doozy. The thing I like to point out is that any software product that stores state has something that can be called a “Repository”. And some marketing hack can call it an “SOA Repository” to make i