Comments on: SOA-REST Wars: The Middleware Menace http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/ Sat, 05 Jul 2008 08:39:18 +0000 http://wordpress.org/?v=2.3.3 By: vmoharil http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-720 vmoharil Thu, 09 Aug 2007 17:29:58 +0000 http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-720 "reusable collection of plumbing bits as opposed to the more common tightly integrated all-in-one stack type affair." Totally agreed - I could not have said it better. “reusable collection of plumbing bits as opposed to the more common tightly integrated all-in-one stack type affair.”

Totally agreed - I could not have said it better.

]]> By: Dan Creswell http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-719 Dan Creswell Thu, 09 Aug 2007 16:07:36 +0000 http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-719 "However, I do believe that the basic plumbing infrastructure pieces e.g. logging, monitoring, caching, configuration, timeouts, connection pools etc. should not be reinvented by each and every “hot programmer” team." Agreed with caveat: Ideally that's the case but for example in a distributed system what that infrastructure looks like is radically different from what one finds in most centralized middleware. When this sort of thing happens it's sometimes necessary to re-invent the wheel a little. I guess what we really want is a reusable collection of plumbing bits as opposed to the more common tightly integrated all-in-one stack type affair. “However, I do believe that the basic plumbing infrastructure pieces e.g. logging, monitoring, caching, configuration, timeouts, connection pools etc. should not be reinvented by each and every “hot programmer” team.”

Agreed with caveat:

Ideally that’s the case but for example in a distributed system what that infrastructure looks like is radically different from what one finds in most centralized middleware. When this sort of thing happens it’s sometimes necessary to re-invent the wheel a little. I guess what we really want is a reusable collection of plumbing bits as opposed to the more common tightly integrated all-in-one stack type affair.

]]> By: vmoharil http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-718 vmoharil Thu, 09 Aug 2007 15:57:04 +0000 http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-718 I completely agree that SOA is not about or should not be about technology. I also agree that the enterprises should avoid the temptation to hire commodity programmers. I am also not a proponent of the WS-* hype created by the vendors to make us believe that the middle ware will take care of all and you just need to write "trivial" custom logic. However, I do believe that the basic plumbing infrastructure pieces e.g. logging, monitoring, caching, configuration, timeouts, connection pools etc. should not be reinvented by each and every "hot programmer" team. That's not the ideal usage of hot programmers. The responsibility should be shared (so that truck factor is more than 1) but there should be minimal (preferably 1) consistent way of doing these "low level yet challenging" things. I completely agree that SOA is not about or should not be about technology. I also agree that the enterprises should avoid the temptation to hire commodity programmers. I am also not a proponent of the WS-* hype created by the vendors to make us believe that the middle ware will take care of all and you just need to write “trivial” custom logic.

However, I do believe that the basic plumbing infrastructure pieces e.g. logging, monitoring, caching, configuration, timeouts, connection pools etc. should not be reinvented by each and every “hot programmer” team. That’s not the ideal usage of hot programmers. The responsibility should be shared (so that truck factor is more than 1) but there should be minimal (preferably 1) consistent way of doing these “low level yet challenging” things.

]]> By: Kelly Denehy http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-717 Kelly Denehy Thu, 09 Aug 2007 14:06:32 +0000 http://www.dancres.org/blitzblog/2007/08/08/soa-rest-wars-the-middleware-menace/#comment-717 I think the enterprise's desire to utilize* commodity programmers has led to a lot of unnecessary complexity, not just in middleware, but in development methodologies, coordinating geographically dispersed development teams (i.e., offshoring), etc. *sorry, Firefox's spell checker insists this is the correct spelling. :-) I think the enterprise’s desire to utilize* commodity programmers has led to a lot of unnecessary complexity, not just in middleware, but in development methodologies, coordinating geographically dispersed development teams (i.e., offshoring), etc.

*sorry, Firefox’s spell checker insists this is the correct spelling. :-)

]]>