earlier replies
Replying to @stilkov
OK. Care to explain? In his model, UI composition is common. SCS use REST mainly? @ewolff @UdiDahan
2
@scsarchitecture relies on browser-based integration, independent of any particular client-side app technology
1
IMO there are UI composition differences, but the rest is very similar
2
I simple love the name: self contained system. What a perfect metaphor!
1
1
it IS a good name. More saying than service
2
Only problem is that "system" implies a unit of deployment, not logic @jeppec @Cairolali @stilkov @trondhjort @ewolff @scsarchitecture
4
1
That’s the main point :) Units of deployment as architecture boundaries
2
But, but... :) Isn't the SCS boundary logical? Not deployment @UdiDahan @jeppec @Cairolali @ewolff
2
Microservices and SCSs don’t treat deployment boundaries as an implementation detail.
2
I though I understood it. How can an SCS be a single deployable unit? Embedded? @UdiDahan @jeppec @Cairolali @ewolff
1
Replying to @trondhjort @UdiDahan @jeppec @Cairolali @ewolff
Doesn't have to be a single unit, but an SCS is always deployable separately from others

Nov 30, 2016 · 7:28 PM UTC

1
Replying to @stilkov
OK. How do you enforce that? That that particular DB is deployed together with that app? @UdiDahan @jeppec @Cairolali @ewolff
3
I think you’re missing the point: It’s key that no DB is shared between two SCSs …
1
more replies