Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

13
  • 7
    An important note: No architecture can save your butt if your devs don't know what they are doing. Even theoretically loose archs can end up a mess of tightly coupled code if you don't take proper care. You can make a loosely coupled monolithic software without a problem if you put in the extra effort. It is just... well, kinda way harder. Commented Jan 18, 2021 at 11:57
  • 4
    to create modularization - Yes, and now that you've done that you don't have a monolithic application any longer. You have a GUI that wraps a bunch of modules. Commented Jan 18, 2021 at 16:36
  • 1
    While you can properly modularize a monolith, the suggestion to just have everyone re-use the DAO is already a step into a not properly decoupled monolith ;P Sharing a DAO across the whole application is typically already considered too tight a coupling, because you expose the explicit data layer to all other components instead of an abstract layer. Have fun changing the data layer and understanding what other components have written in your structures, why and what assumptions they make about the data returned on that level that. A dao should only be shared in its component. Commented Jan 19, 2021 at 5:34
  • 2
    @J... - that's nonsense. We've been building modular monolithic applications for half a century before microservices hype. Commented Jan 19, 2021 at 16:13
  • 2
    @J... - it absolutelly isn't, and the only way it's contradiction if you use your own made up nonsensical definitions. Monolithic application is not one that is written poorly. Commented Jan 19, 2021 at 16:30