I personally don’t recall anyone advocating tons of tiny (a few 100 LOC) services before, one for each single feature.
7
1
3
@stilkov What do you think MSA adds that’s not covered by SOA principles?
2
@kellabyte But if they’re not micro, they’re just services //cc @martinfowler @boicy
3
@stilkov Ich nutze hier MVVM um das Problem zu minimieren, QL.io geht das deklarativ an: ql.io/examples
1
Replying to @DesignedByBlind
@designedbyblind ql.io is a nice way to orchestrate microservices in my mind (switching back to English for @kellabyte’s sake)

Mar 17, 2014 · 2:52 PM UTC

2
1
Replying to @stilkov
@stilkov @kellabyte Some of our micro services had to be refactored to share more data: meshing e.g. places API with other APIs where slow.
2
@designedbyblind @kellabyte Main reason for my skepticism about the “micro” aspect: Can’t see how to make fine-grained calls perform well
2
more replies
Replying to @stilkov
@stilkov @kellabyte it's a good remedy for issues of micro services: data model vs view model, and their inefficient cartesic combinations.