Sadly, many systems made of "restful microservices" aren't that modular either. Request/response = tight coupling. HTTP doesn't change that.
Stefan Tilkov @stilkov
21 Oct 2017
Replying to @UdiDahan
True, in theory, deployment monoliths can be highly modular internally. Sadly, in practice they often are not
4
34
2
39
So, what's the solution? Pub/sub on the backend and view-model composition on the front-end. See how it's done: github.com/Particular/Worksh…

GitHub - Particular/Workshop: SOA Done Right

SOA Done Right. Contribute to Particular/Workshop development by creating an account on GitHub.

github.com
3
9
2
30
I agree, although I assume we still differ a bit on how exactly to achieve that front end integration
1
If you dont agree with doing a composite UI then what would you suggest?
1
Replying to @ColinPear @UdiDahan
I prefer to rely on plain Web integration. IIRC, Udi’s approach relies on shared components in a GUI app.

Oct 21, 2017 · 1:08 PM UTC

1
1
Replying to @stilkov @UdiDahan
This sounds like you are saying you cant do composition in a plain website/web application. Is that what you mean?
1
No, on the contrary. I believe that’s the only environment that allows for standard-based integration comparable to the one in the backend