News for hackers. Stuff that matters.
Re:Matrix of Services by dragonwriter on Thursday June 19, 2014 @03:03PM (#7917729)
> The old version of SOA focused on defining the protocols and API's that services would use to communicate, from the top down. There was a lot of effort put into standardized object definitions and CORBA and EJB, and standardized protocols like SOAP.

I think that CORBA and EJB are sort of the institutionalization of the SOA concept, in much the way that rigid, top-down practices like Scrum are part of the institutionalization of Agile.

I don't think original SOA was any more heavyweight, top-down than original Agile; I think people tend to naturally gravitate toward centralized, top-down ways of doing things, producing a natural cycle of "back to basics", followed by centralizing, top-down approaches trying to impose more definition and manageability on the "new" approaches. (And are aided in this by tool vendors, who want people to buy exclusively into their tools rather than have heterogenous environments, for clear commercial reasons.)

There's also new techniques that develop in parallel to the cycle and stop the cycle from strictly being reinventing the wheel, usually, but the basic pattern is largely cyclical.

> Services from many different languages and platforms co-exist. That's the whole idea.

That was a widely touted feature of old SOA, and of earlier (but by now somewhat old) reactions to the way old SOA went as heavily platform dependent services became common in it.

There are no comments on this comment yet.