This post originated from an RSS feed registered with Java Buzz by Michael Cote. Original Post: Pipelining Feed Title: Cote's Weblog: Coding, Austin, etc. Feed URL: https://cote.io/feed/ Feed Description: Using Java to get to the ideal state. Latest Java Buzz Posts Latest Java Buzz Posts by Michael Cote Latest Posts From Cote's Weblog: Coding, Austin, etc.

An interesting article over on InfoWorld (pardon the choppy sentence there). I haven't had time to think too much about it, but it made me think that there's been a real trend lately, in the trade rags and anaylist chatter, towards system integration. Maybe it's just blind excitement, as usual with the integration topic. At the very least, the integration focus seems to have a more componentalized motif than usual: that is, instead of just saying "businesses want/need to integrate their IT/applications," the actual architectural notion of the integration being extremely component based seems to be creeping up.

Or maybe I'm reading too much into it. At the very least, "everyone" seems convinced that your product must be able to talk with other products, by (1.) at least inputting and outputting data real-time, and, (2.) on the frilly end, they should be able to tell each other to do things. One can imagine that missing piece is that, from a high-level perspective, you'd never know you had seperate products, you'd just have "The Business Process," but that's pretty pie-in-the-sky at the moment.