earlier replies
Replying to @csterwa
@csterwa No, I’m claiming that Fowler is rewriting history, ignoring the best part of a decade and attributing to the last few years only.
3
@dancres although micro-services arch pattern has been impl for decade++, Fowler refs May 2011 Venice mtg where term came up
2
@csterwa @dancres It seems the *term* dates from 2011, but the concept, of course, goes back to at least Unix @boicy
5
@martinfowler @csterwa @boicy Okay, what’s the value of encouraging the use of a new-term for an old practice/concept/approach?
2
@dancres What term do you suggest should be used instead?
2
@stilkov SOA. It’s just services: queue.acm.org/detail.cfm?id=…
2
3
2
@dancres Fair enough. SOA is more often thought to mean enterprise-wide integration and much bigger services, though.
4
@stilkov @dancres @trondhr but that's just a misconception. EAI as applied in most Enterprises has nothing to do with SOA
1
2
@jeppec @dancres @trondhr Who has authority to define what SOA is or isn’t?
3
@stilkov @jeppec @trondhr Wrong question for me. More useful is why we repeat history and overload terms preventing forward motion.
1
1
Replying to @dancres
@dancres @jeppec @trondhr Maybe we just need to stop being offended by seeing new labels put on only slightly different stuff.

Mar 14, 2014 · 8:43 AM UTC

2
Replying to @stilkov
@stilkov @jeppec @trondhr Oh, I believe the problem is we’re not offended enough. :)
Replying to @stilkov
@stilkov @dancres @trondhr IMO the overlaoding is not a problem. It's the lack of guidance and repeat of old mistakes using new technology
2
1
@jeppec @stilkov @trondhr Think both are symptoms of some basic fails: be a student of history, do some analysis, focus on clear comms.