4 ms·

Monoliths always sound like a good idea but they always lead to some low code platform garbage that the org has settled upon. Microservices stay as proper code

• fendy3002 6y ago
  Gotta disagree with you. A well built / designed / simple monolith beats any poorly implemented microservice of the same domain problem anytime. If you cannot separate the domain problem correctly in microservice architecture, be prepared for the worst.
  • flarg 6y ago
    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.
    • fendy3002 6y ago
      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.
      • flarg 6y ago
        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.