.@scsarchitecture I just listened to innoq.com/de/podcast/025-scs… I ask myself why you don't name the replication of data as an alternative to including parts of the other system's UI. It's a good approach to bypass the frontend integration problems, isn't it? /cc @ewolff @stilkov

Self-contained Systems und Frontend-Integration – Teil 1

Self-contained Systems (SCS) stellen einen Ansatz zur Modularisierung von Systemen dar. Sie übernehmen viele gute Ideen des Microservices-Konzepts. Eine wichtiges Element ist die Frontend-Integration...

innoq.com
1
/cc @tillsc @nothing_box
2
Replying to @OliverLibutzki @tillsc @nothing_box
Yes, that’s a good option, too, if you make sure you know where data is mastered, and we use it often. The downside is that you have to take care of synchronization, something you don’t have to do if you do FE integration. Still, both have their place.

Dec 6, 2018 · 9:31 PM UTC

1
1
Replying to @stilkov @tillsc @nothing_box
Having bounded contexts which interact using domain events is a good choice as the SCS can pick the data which it is interested in by itself. Having such an architecture lowers the need to use these cumbersome frontend integration strategies.
1
I don’t find them cumbersome at all in many situations. IMO they’re often the cleaner and simpler option, and often reduce coupling. Sometimes they’re not, no tool works for everything.
1
more replies