Hi,
Some background, we are busy restructuring our system architecture and currently all of our logic sits within our main application (module), we only have one module but over time the system got very bloated and we are now splitting up the main module into separate modules.We come from traditional software engineering backgrounds and our plan is to create API's for our modules to send and receive data between each other.Is this a good idea or should we rather just share server actions between modules?Kind Regards
Werner
Hello Werner,
So, in order to break down that monolith, you will need to come up with the concepts/domains segregation.
After this initial phase of disclosing the different domains, what can be done is that inside the same domain, it's ok to use public server actions, but between domains, one should use service actions (weak reference) or REST API as wrappers of the server actions.
This will facilitate the deployments to other environments also.
Please take a look at the documentation recommended by OutSystems for the Architecture Specialization, this will give you more insights on how to distribute the concepts and build a sound architecture (attached).
Best Regards,
PZ
Thanks so much Paulo, I think we're going to stick with REST API's for now.
Hello,
Glad that helped you. Be my guest to expose here your doubts or curiosities about the platform in the forum. I'm sure the community will always help you in the best way possible.
Regards,