-
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 »
Warning: This article requires a lot of editing love before it is very useful. It might be somewhat incoherent. Read at your own risk. ;-)
Silo (software): A silo system cannot easily integrate with any other system.
In software, the term “silo” is used to ... Continue reading »
Silo (software): A silo system cannot easily integrate with any other system.
In software, the term “silo” is used to ... Continue reading »
5 months ago
Fact 1: "Each layer was added in an attempt to make it easier for someone to integrate with the system. Each layer makes the whole harder to understand." Would you call this a silo? Each layer is probably added for, and probably serves, its purpose of adaption or adding value. Different layers may exist in parallell or on top of each other. New and different integration needs may solved on top of previous, lower layers. That seems natural. Unless you only conceive the top as being "the service".
Fact 2: Important learning. Silos may be only apparent and present integration interfaces. Thanks.
Fact 3: Yes, few examples of successful, euphoric, large-grained integration and reuse exist, and probably for good reasons. But isn't there an agile, medium-grained middle way between that and silo thinking?
Ode to silos that in fact aren't and to agile, timely integration?
5 months ago
The people responsible for a single layer generally seem to consider themselves service providers for the layers above.
This is not a agile way of creating software. But it's a common implementation of medium-grained SOA services.
Thanks for the kind words, Eivind. Your closing remark is exactly what I wanted to express.