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
Load newest
Replying to @stilkov
@stilkov There’s a bunch of blog posts that talk about an object per service, 100 LoC per service etc from various folks.
Replying to @stilkov
@stilkov I’m honestly still trying to figure that out.
1
Replying to @andyhedges
@andyhedges @martinfowler @stilkov @boicy Exactly!
Replying to @stilkov
@stilkov as @boicy explains in vimeo.com/m/74452550 I have a feeling the features are a bit bigger than a couple of 100 LOC
Replying to @stilkov
@stilkov if you s/service/process/ you have a pretty good description of Erlang, which is only 20-something years old.
1
1
Replying to @stilkov
@stilkov Isn’t it about each (micro)service doing just one thing, rather than LOC?
2
@coreload @drunkcod @jbrains Indeed. Distilling down SOA for other successful elements could be useful. No need for a new name though.
Replying to @stilkov
@stilkov There was a talk about that on BaRuCo 2012. youtube.com/watch?v=2rKEveL5…
1