earlier replies
Replying to @dancres
@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
@trondhr @UdiDahan @dancres I’m also not really convinced having a few hundred microservices yields a good architecture.
1
1
@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 @dancres totally agree. The current guidance on lines of code alone is absolutely horrible. It ignores so much
1
Replying to @jeppec
@jeppec @trondhr @udidahan @dancres I agree as well. But I believe @martinfowler and @boicy would too

Mar 14, 2014 · 8:45 AM UTC

1
Replying to @stilkov
@stilkov @jeppec @trondhr @UdiDahan @dancres @martinfowler I certainly would - size about team skill, ops maturity and actual requirements
2