-
Website
http://www.brodwall.com/johannes/blog/ -
Original page
http://www.brodwall.com/johannes/blog/2006/06/11/why-i-hate-soa-in-less-than-200-words/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
eirikma
2 comments · 1 points
-
Affordable SEO Services
1 comment · 1 points
-
andreb
1 comment · 1 points
-
thommyb
1 comment · 1 points
-
Andy Palmer
1 comment · 1 points
-
-
Popular Threads
But, assuming a component has callers outside of a single application, how can you avoid defining a contractual interface? If components didn't have responsbilities and defined interfaces, developers calling those components would have to understand the internals of every single one of them. In a large system, that's just not realistic.
Sure it can be taken to an extreme, but what's your alternative?
If you are going to be used by an external application, sooner or later you will have to publish a contractual interface. However, I find that most developers break up their systems into too many applications with external interfaces before this is necessary. As long as you have a well-defined group, it's no problem to have 20 or more people using continuous integration to stay agile for a long time.
I guess my point is that: Yes, if you need to communicate with an external application, you need a contractual interface. But my experience is people overestimate the need to communicate with the rest of the world. (This is of course an observation from in-house development, I expect shrink wrap to follow different rules)