123
Views
4
Comments
Monolithic Service Module
Question

Hi

i have one core Module and in this module i have only 6 entities and 20-25 Server Action and 30-35 Structures we have and module size is 1.5 mb but still it is showing it is monolithic module. What is the reason behind this? Is there any threshold to identify as Monolithic module?


what is the reason behind this if module is big and to many public action then i can understand but why it is coming for this module not able to underdstand.

2019-01-07 16-04-16
Siya
 
MVP

Please refer to a similar discussion at https://www.outsystems.com/forums/discussion/74547/threshold-monolithic-service-module/

as per this post, there isn't a fixed threshold for the number of public elements in a service and recommends careful analysis of business concepts to decide if they should be grouped together.

2023-06-14 08-52-52
Arkyadeep Bharadwaj

Hi Siya

Thanks for replying. But my question how it is identifying.

I have one product core module and under that we have different product like credit card,IPO etc and that module size is 2.5 mb and we have public action. we have Product module and under that we have different product related action.if there is no threshold then how it is identifying monolithic this is.i can understand under one we have different product it should under different product module but if we have less functionality then we can combine in One module right. 

2019-01-07 16-04-16
Siya
 
MVP

There isn't a definitive threshold. You have two options: either refactor into separate modules or, if you're confident in the current structure, mark it as a false positive.

2024-05-02 11-20-07
Bas Klein

The classification of a module as “monolithic” in OutSystems is not just about its size or the number of public actions. It also takes into account the complexity and interdependencies within the module. Even if a module is not large in size or does not have many public actions, it can still be classified as monolithic if it has complex logic or numerous interdependencies. It’s always recommended to keep modules small, manageable, and with a clear separation of concerns to avoid them being classified as monolithic. 

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.