Hi Vrat - the single/mega object design is not 'wrong' but it can lead to problems. Over time a single object can grow to become an unwieldy lump that is slow to load, hard to understand and maintain, and slow to save. It can also become a 'single point of failure' when shared by many processes.
At BP our original thinking was 1 app = 1 VBO but over time, as we worked with the same clients over 10+ years, we ended up with some giant VBOs that had become a burden. We realised that a modular design would have been better (easier collaboration, lightweight, lower risk of breakages etc) but because the VBOs were used by very many Production processes, there was no business requirement or 'risk appetite' for fundamental design changes.
But if you know that your VBO will not need to be reused and will be developed by one person, then the single object design can work, if that is your preference. Our recommendation is adopt a small/modular design approach because experience has shown it to be better. Others may disagree and they are free to make their own choices.
------------------------------
John Carter
Professional Services
Blue Prism
------------------------------
