I personally don’t recall anyone advocating tons of tiny (a few 100 LOC) services before, one for each single feature.

Mar 16, 2014 · 5:10 PM UTC

7
1
3
Replying to @stilkov
@stilkov What do you think MSA adds that’s not covered by SOA principles?
2
@kellabyte I’m not sure I know what SOA principles are. In fact I’m not sure anyone does.
3
Replying to @andyhedges
@andyhedges Not sure how to google for that. And I was referring to the last couple of years, when the microservices term was created.
Replying to @andyhedges
@andyhedges Yes, with “before” I wasn’t referring to @martinfowler’s article, but the SOA discussions of 200x.
Replying to @andyhedges
@andyhedges But that’s in line with his claim (“in the last few years”)
Replying to @andyhedges
@andyhedges @kellabyte Sure, provided two services need to share state. Seems to be in line with the “App” concept in 12factor.net
Replying to @andyhedges
@andyhedges @kellabyte I agree with both of you, and always advocated for the same thing. But not sure this was ever part of mainstream SOA.
Replying to @andyhedges
.@andyhedges @kellabyte There is zero respect left for SOA among the majority of people I talk to, especially in non-enterprise communities
1
2
2
@coreload I can see using microservices to preserve the option to deploy smaller units.
@coreload This seems to make correctness easier now and distribution earlier later.