earlier replies
Replying to @csterwa
@csterwa martinfowler.com/articles/mi… - “We've seen many projects use this style in the last few years” - contrast with: queue.acm.org/detail.cfm?id=…
1
1
2
@dancres to clarify for myself on tweet size - Fowler's article is after-the-fact w/ little history info & Vogels includes history detail?
1
@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 Disagree. Many regard services as a logical and the microservices are their physical comp, ACs in @UdiDahan's model. @dancres
4
1
1
Replying to @trondhjort
@trondhr @UdiDahan @dancres I’m also not really convinced having a few hundred microservices yields a good architecture.

Mar 14, 2014 · 8:35 AM UTC

1
1
Replying to @stilkov
@stilkov I think it is absolute madness to split the code based on size alone, that is why I do not like the term. @UdiDahan @dancres
2
1
@trondhr @stilkov @UdiDahan Concur, there’s transport costs, coupling and all sorts in there.
2
more replies