Initial thoughts for the New Year

Like most people, I get really busy around the holidays and I fell off the blogging wagon. But I'm getting back on it, starting with this post wishing all a Happy New Year! That said, here are the big topics I was thinking about over the holidays...

Like many people, I've been thinking about what's going to happen in the WS space this year. While progress on standardizing WS-* continues, it doesn't seem possible that it would be complete by the time major vendors ship support (only WS-Security has completed the process and from the looks of things WS-Addressing is going to take a while). I think the standardization process is pretty important; it found enough issues with SOAP, WS-Sec, and WS-Addr to suggest that it's worthwhile (WSDL 2 being the major argument against).

But like many pragmatists, I don't care about standards nearly as much as I care about software that offers the features I want. That said, I don't know whether I want a lot of the features that vendors are offering. I keep wondering whether WS-* will repeat the process of COM+ and J2EE, where people invested a lot of time and money only to discover that the basic technology - SOAP, WSDL - was all they really needed. Certainly with Amazon and EBay making money hand-over-fist using basic Web services (or even XML over HTTP), it's hard to argue that you need all of WS-* to successfully reach a business goal.

My prediction is that security enhancements and collaboration - building systems that use multiple services (which could be called orchestration, if that wasn't tied to BPEL in the minds of many) - will be the big features for developers this year. That and of course figuring out how to write schemas that others can use and how to version services in a reasonable way using the toolkits they have today.


Posted Jan 14 2005, 09:48 AM by tim-ewald

Comments

mearls@hotmail.com (Michael Earls) wrote RE: Initial thoughts for the New Year
on 01-14-2005 11:03 AM
Thanks for the thoughts. It seems 2005 will be a year for simplifying things. I've seen a lot of posts like your suggesting that maybe we've taken some of this stuff too far. I think you've hit on a very important point and I'm looking forward to new insights as they're revealed.

Welcome back!
RichB wrote re: Initial thoughts for the New Year
on 01-14-2005 2:35 PM
Perhaps XML over HTTP is too much? Several companies (including Google) employ javascript arrays-over-HTTP.

My personal view is that there's something for everyone. Just as only a small number of systems require assembler, so it follows that only a small number of systems require basic structures-over-HTTP for extreme high performance.

Everyone else makes do with C, C# or Python and likewise the benefits of a higher level API to Web Services makes complex WS scenarios quicker to develop and easier to maintain.

Last year I worked for a company whose website did Javascript arrays-over HTTP for high perf, however I worked on a SOAP interface for 3rd party developers. Some of the future projections of traffic for the SOAP interface were scary in terms of bandwidth requirements. Perhaps XML is too heavyweight?

Having said that, Google successfully provides a RESTful XML search API to some of the other big search engine players and the bandwidth issue doesn't seem to affect them.
Richard Veryard wrote re: Initial thoughts for the New Year
on 01-15-2005 4:14 PM
" ... building systems that use multiple services (which could be called orchestration, if that wasn't tied to BPEL in the minds of many) ..."

Why don't you call it composition?


Commonality wrote Tim on WS-* standarization
on 01-16-2005 5:39 PM
Tim Ewald has a good new post that touches points on the WS-* standarization process. Two things I liked: "While...
Tim wrote re: Initial thoughts for the New Year
on 01-17-2005 7:00 AM
Richard,

You're right, I could have used the term "composition". For some reason I was thinking "collaboration", which didn't sound right, and "composition" just never popped into my head. :-)

Tim-
Jon Fancey wrote re: Initial thoughts for the New Year
on 01-17-2005 2:09 PM
Happy New Year Tim - welcome back!

I agree with your predictions I think this year will really see service aggregation occur as people and companies cut their teeth on exposing fine-grained services within their enterprises to provide that base-level to build upon. I for one am very interested to see if we can achieve the high levels of reuse with this technology that we've failed to with others in the past. If we do, it's gonna snowball..

BPEL is all about service collaboration and composition. Sure it's misunderstood and it'll go through some changes before its done but I firmly believe its a step in the right direction because of this. I think where people get BPEL wrong is in thinking that it's meant for business process definition. Look at BizTalk, it has the concept of orchestration at its heart. Orchestration is something that will touch most developers over the next few years I believe.
on 01-18-2005 6:38 AM

Add a Comment

(required)  
(optional)
(required)  
Remember Me?