Re:Modern-Day Architecture Design Patterns for Software Prof...
by flarg on Wednesday October 14, 2020 @10:18AM
(#24776779)
Gotta agree with you - but my point was 'low code garbage' - this is what happens in enterprises if a monolith is the goal; if you rule out monolith then you ain't suffering with Pega, Appian, Salesforce etc. Monoliths are great but they are also an open manhole you need to close in enterprise development.
Re:Modern-Day Architecture Design Patterns for Software Prof...
by fendy3002 on Wednesday October 14, 2020 @10:39AM
(#24777010)
A giant shithole is what you get when you create a monolith that can fit into many business processes / cases. One additional case to handle introduce many more complexity to application.
Re:Modern-Day Architecture Design Patterns for Software Prof...
by flarg on Wednesday October 14, 2020 @04:25PM
(#24781150)
For sure. Next after selecting a low code monolithic stack we are informed that we can reuse low code solution, which is like a doubling down on the monolithic approach. But of course with 30 consultants.
If you cannot separate the domain problem correctly in microservice architecture, be prepared for the worst.