Could you please explain a bit about the role of controller? Usually, some business logics are in the controller, you said the business logic would be in the model. Please explain a bit, if possible, with an example. Do you have a sample app build with the new architecture that we could take a look at and understand?
The controller is responsible for interfacing with the DX API to get and push data to the server as well as interpret the responses from these APIs and generate the UI screen to render by calling the appropriate components.
Currently, when we configure a flow, we have both the business logic and the UI (flow action)? is this going to change as the UI interaction is done via DX API?
Keeping the business logic is fine (decision shape, when rules...). We want to limit the amount of logic that goes into the section rule form right now - Using when rule in a section to change the container format or the type of icon being rendered is an example of business logic stored in the presentation layer
Can we get some information on new UI service? Assuming it’s a micro service, is it deployed in separate container or node?