-
Subscribe -
Community
-
Top Commenters
-
Popular Threads
-
Recent Comments
- Thanks for your comment. I've encountered people who talk about non-distributed SOA. I think that is an idea that is totally boring, as it says nothing that hasn't been said for twenty...
- In the text you, like most I think, define services to be distributed. I do not understand why everybody i
- Hi, Eve Thanks for the offer. Let me know if there's any way I can make it easier. Do you think I should consolidate all the articles into one, for example?
- I'd be more than happy to read drafts, run through example code, and whatnot. I've done a little bit of Rails work, but I'm enough of a noob that I'll be able to give good feedback...
- I've never had much luck with the precreated keys. But then again, I use the convention of a null-key to indicate unsaved objects, so I'd run into other problems. FWIW, it sounds like your...
Jump to original thread »
On JavaZone 2005, I talked about “Why I hate SOA”. I found it hard then, and I’ve still found it hard for a while to express this sentiment concisely. I think I’ve finally got it!
One of the most common inefficiencies I discover in organization ... Continue reading »
One of the most common inefficiencies I discover in organization ... Continue reading »
2 years ago
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?
2 years ago
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)