The Artima Developer Community
Sponsored Link

.NET Buzz Forum
Service Oriented Weakness

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Udi Dahan

Posts: 882
Nickname: udidahan
Registered: Nov, 2003

Udi Dahan is The Software Simplist
Service Oriented Weakness Posted: Oct 4, 2005 10:11 AM
Reply to this message Reply

This post originated from an RSS feed registered with .NET Buzz by Udi Dahan.
Original Post: Service Oriented Weakness
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple. This blog is about how I do it.
Latest .NET Buzz Posts
Latest .NET Buzz Posts by Udi Dahan
Latest Posts From Udi Dahan - The Software Simplist

Advertisement
So you've swallowed the SOA koolaid, you're the best MEST'er there is, and you're all ready to begin your first, full-blown, SOA project. Well, you've obviously read "MEST up", and you're ready to pub-sub your way to glory. There's just one, teeny-tiny thing that may have slipped by you: the GUI. That client-side code that just ISN'T a service. It may sub, but it sure ain't pubbin'. There's also those nasty multi-threading issues that you just can't get around. The user WILL click when a message comes by and updates that very same object you want to refresh. Even when you get past all that, you've got to accept the fact that the client will never be loosely coupled like other services. Not only that, a large section of a given service's contract will exist solely for the client. May this post be one of many (by me and the rest of the guys down in the trenches writing the code that will be called service oriented) to take down the SOA/ESB/EDA/"whatever TLA comes next" hype. I'm sick of business people arguing architecture with me after returning from their last, vendor sponsored, SOA conference. We do software. We've been doing it a long time. We will continue doing it after this hype, and many after it, wither and die. We do not try to tell you how to run your business. Please, stop telling us how you think the software that runs your business needs to be technically built. Please DO tell us what the software should do. Good requirements are hard to come by, SOA or not. Oh, and to all the vendors out there, where do YOU get the audacity to tell us how the software that runs our businesses should be built - with nary a requirement to be seen? Wow, that's been building up for some time. Good to get it off my chest....

Read: Service Oriented Weakness

Topic: .Net Developers Group Meeting in OKC October 1st Previous Topic   Next Topic Topic: D4 Software Frameworks - A Pattern Language

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use