We all are familiar with AI Mentor Studio warning "Monolithic Module" which occurs when too many public elements or concepts or processes are contained in single OutSystems module. Such modules are likely to pose problems like hard to maintain, interference with lifecycles, impacts on consumers etc. In this session we will talk about a real project scenario where a core business module became a monolith and began to impact the stakeholders. After pushing it back for several months, finally customer agreed to break it down. However being a core business module, any refactoring work on it was likely to impact almost the entire application, making it even more challenging. We were asked to come up with proposals for this refactoring while ensuring:

1. Refactoring must not impact the entire system.

2. Should be able to accommodate new development in between refactoring phases.

3. Avoid rework for teams. We will talk in detail about different proposals, pros & cons for each and more.

We’re inviting JUNAID SYED to talk about the Break Down Monolith - Different Strategies at our OutSystems User Group Nagpur

RSVP today to get free entry tickets