Spider Plague Closes Australian Hospital :: WRAL.com

Spider Plague Closes Australian Hospital :: WRAL.com. Seems like something out of one of those B horror movies. Of course I did notice in the article that warm weather was to blame....which means this will end up being attributed to Global Warming. Just think, spiders will take over the earth in the next 50 years because we drive to much. Who would have ever made that link? Personally I'd rather go via a redback spider than drown in the rising sea. Of course this brings up another point, going green. If we go green and it actually reduces the earth's temperature, what impact will that have on the redback spiders? I'm sure the redbacks don't have an advocacy group yet but just wait.

It's the data

I'm stating the obvious here but the underlying key element to services is the data. Agility, reuse, composibility and all that other jazz is difficult to achieve when you do not really understand the data. Chris Madrid has posted an article on Master Data Management over at SOA Magazine. I think Chris's points on the issues facing the enterprise are outlined very well. Multiple sources of the same or variations of the same data are the heart of the issue. Keeping them in sync and knowing which one to draw from can be difficult at best. The solution as outlined by Chris, is basically a central repository that serves as the master data. A very noble cause within the enterprise.

I think there are a few issues with this that some enterprises will run into. Does the enterprise actually have data architects? I going to throw out there that surprisingly few do. That can be a problem. Developers, DBA's and even Enterprise Architects don't always make for the best data architects. And even when they do understand it very well, it's usually not their primary focus. Moving to the Master Data Management concept requires resources that are focused on just that. This leads to the next issue which is buy in. Can you get the enterprise to agree on the concept and if so can you then get them to agree on the data model?

I don't think the issues facing Master Data Management are all that different from the concepts of a Common Information Model. It can be a large black hole for an enterprise. Attempting something like that a can turn into a long effort that ultimately doesn't keep pace with the changing business and is outdated before it's even put into place. I do agree with the concept though and I think the closer you can get to this state the more successful your SOA can be.

Red Hat bails on consumer Linux desktop | Tech news blog - CNET News.com

Red Hat bails on consumer Linux desktop | Tech news blog - CNET News.com. I won't say I told you so but I told you so. That market is just to tough to crack without throwing tons of resources at it. Apple has that ability, Linux does not.

First PC? Or was it a MAC?

It was 20 years ago today: Not Sgt. Pepper, but my PCjr | Coop's Corner : A Blog from Charlie Cooper - CNET News.com Charlie Cooper posted this entry on his first PC. It started me reminiscing about the old days. I had a Timex Sinclair ZX81. It was hooked up to a cassette recorder and a small portable TV. My first BASIC programs solved quadratic equations and graphed Sine waves. I thought that was very cool. My neighbor on the other hand, who was a year younger than me, had a TRS-80. He wrote a BASIC problem to automate his father's drug store. Just slightly different skill levels. :)

Practical Service Design

One thing I've noticed over the last year is the continued lack of resources on detailed service design. There are plenty of resources geared at the architecture layer but very few geared toward the person actually doing the coding. I am hoping over the new few months to share some of my practical experience and pose some questions I still ponder on the details of service design. I'll also share some links on the Web that I have found to be useful.

If you do the actual design and implementation of services, please feel free to chime in with your own experiences. There is no one right way to do it. Good dialog on practices is always beneficial.

I'm in the middle of some major projects at work so I'm not sure when I'll get started. I want the content to be detailed and useful so it could take some time. In the meantime I'm very excited about the new book coming from Thomas Erl on Web Service Contract Design.

Linux PCs?

Here is a story over on yahoo about the emerging Linux PC. I'm a big fan of Linux and Open Source software in general. However Linux on the average consumer's(that includes business users) desktop is just not going to happen other than in the niche its already in. The only vendor that has made any dent (small dent) in Microsoft's PC OS realm is Apple. You can make arguments all day long about the differences in the technology but it makes little to no difference.

It would be like your favorite local brew pub going against Anheuser-Busch. Of course I will look back on this in 10 years to see if I just completely missed the boat but somehow I don't think so.

Common Information Model

The idea of a Common Information Model to rule all within a business has been around for a long time. It's gained a lot more traction recently with SOA. Here is a post from Nick Malick at Microsoft and some of their efforts. His post is part of an ongoing conversation with Alex Maclinovsky at Sun.

They both bring up good points but I find myself leaning towards Alex's realism a bit more. I can bring up the point that the average business IT shop does not have a lot of luxuries when it comes to time. CIM's take time... a lot of time. They also take knowledgeable data architects, expert negotiators and the ability to bend the space time continuum. Simply out of reach to most IT shops.

Would a large model that rules all hold up to the daily demands of the constantly changing business? I know the academic arguments around versioning, governance etc but that within itself can be difficult even with a governance product. By the way Microsoft has a new product in this space, only for MS products though. :(

I've stated before that one size doesn't fit all meaning what works for my organization might not work for yours. I have found that smaller simplistic data structures combined with more granular services can achieve a lot of flexibility and reuse. These can be wired together to make more coarse grained services but the reuse tends to go down and the complexity goes up.

Ultimately data translation and manipulation has to happen anyway to satisfy the needs of the off the shelve systems as well as old legacy systems. Some common simplistic data structures can help with that without having to go for the big bang approach that a CIM can create.

Upgrade Time

My home server is in need of an upgrade/replacement. Here is a picture of it (Notice the cool steering wheel). I think my mobile phone has more RAM than it.

Home PC

It's served me well for the 100+ years its been around but I'm thinking time for a upgrade plus I'm getting tired of the black smoke coming out of it. Don't get me wrong the three laptops in the house have more than enough computing power for my everyday use. But the keeper of the blog needs a little more juice. Plus the OS it's running on needs a little upgrading as well.

I haven't decided what its new platform and OS will be, I'll have to do a little pondering on that. SUSE has served me well but I might want to shake it up a bit just for the grins of it. I'll keep you posted on my pondering.

How's SOA?

This seems like a strange question since most field IT folks (not analysts) are still not really sure what SOA is or how to implement it. Is a year really long enough to give organizations time enough to get their stuff together? How many IT shops have the luxury of stopping time and focusing on changing the way they build applications? Isn't SOA really an iterative journey over a longer period of time? Todd Biske wrote a very good post on Setting SOA Expectations.

Todd was inspired by this post from Anne Thomas Manes who was looking for SOA success stories. Although Anne painted a pretty bleak picture I not sure enough time has past to call it a day and move on to the next set of buzz words. This quote from Anne in particular got me thinking:

This company reorganized IT around functional capabilities (rather than business units) and established strong positive and negative incentives that encourage people to adopt a better attitude toward sharing. I'm beginning to think that this is the only path to SOA success.

I not sure I would go along with this train of thought. The dynamics of a company, the personnel in the IT shop, the business landscape the company plays in, the size of the company are all factors that shape the way an IT shop functions. There is no one size fits all. What works for one organization is probably not going to work for another. Still I think there is potential value to be had on the road to an SOA style of architecture and the sharing of best practices. That doesn't mean all best practices will work for us or are required for us to derive value.

Okay my next post will be back to more technical in nature(XML Schema). I know you can hardly wait, XML Schema discussions make for such fun dinner conversation.

It's Back

It's been a year since I shut down the blog. I'm finally starting to settle in at my new company so I thought it would be a good time to get going again with the blog. I can't believe a year has gone by so fast.

The IT shop is much smaller than my previous one but the intensity is much higher. I was brought in to jump start the webMethods practice and that's what we have done over the past year. I've spent most that time developing rather than architecting and it's been a blast. There is just something about being hands on that just can't be beat.

In addition to webMethods, I'm really focused on Web Services right now and in particular XML Schema design. Stay tuned for more on that.