Steve Jones jones.steveg@gmail.com [service-orientated-architecture]
2015-06-29 23:03:20 UTC
On 29 June 2015 at 13:29, Nick Gall ***@gmail.com
[service-orientated-architecture] <
which is one definition, and has been used), qualifies out business
architecture (which I disagree with) then you say lets go back to
ignoring....
anti-patterns on what doesn't work.
http://www.itbusinessedge.com/cm/blogs/lawson/the-three-best-examples-of-successful-soas/?cs=16305
has three examples that Anne thought were worthy, and a quick google will
find many more, that one even references you and your call at the time for
WOA as the answer BTW.
Steve
[service-orientated-architecture] <
[service-orientated-architecture] <
detailed examples of realized OASIS-defined SOAs, that aren't just everyday
businesses offering everyday services, let's PLEASE go back to ignoring
SOA."
The start of that statement includes a restriction (must be OASIS defined,[service-orientated-architecture] <
about learning.
I said, "So until someone provides a significant number of concrete,[service-orientated-architecture] <
people to learn from it's shortcomings.
You said that we should get on with ignoring it... hard to say that is[service-orientated-architecture] <
approaches like OO and SOA makes zero sense. Linking current thinking to
its historical routes and highlighting what worked and what didn't is at
the heart of progress.
Who said anything about ignoring the history of SOA? Not me. I want[service-orientated-architecture] <
I do think that saying we should ignore learning from historicapproaches like OO and SOA makes zero sense. Linking current thinking to
its historical routes and highlighting what worked and what didn't is at
the heart of progress.
people to learn from it's shortcomings.
about learning.
detailed examples of realized OASIS-defined SOAs, that aren't just everyday
businesses offering everyday services, let's PLEASE go back to ignoring
SOA."
which is one definition, and has been used), qualifies out business
architecture (which I disagree with) then you say lets go back to
ignoring....
That would include "highlighting what worked and what didn't" in concrete
and detailed terms from actual implementations of SOA.
Of which a quick Google will find you a bunch, starting with theand detailed terms from actual implementations of SOA.
anti-patterns on what doesn't work.
But do people contribute such post-mortems to this group? From actual
business people who implemented the SOA? With case-study-level details, not
just platitudes about how successful their SOA is?
Not sure a Yahoo email list is the right place to publish case studies....business people who implemented the SOA? With case-study-level details, not
just platitudes about how successful their SOA is?
http://www.itbusinessedge.com/cm/blogs/lawson/the-three-best-examples-of-successful-soas/?cs=16305
has three examples that Anne thought were worthy, and a quick google will
find many more, that one even references you and your call at the time for
WOA as the answer BTW.
Never. Instead we get pissing matches like this one.
THAT'S why I said ignore SOA and this group. And now I'm going to follow
my own advice.
Ciao.
-- Nick
ByeTHAT'S why I said ignore SOA and this group. And now I'm going to follow
my own advice.
Ciao.
-- Nick
Steve