After careful deliberation, we’re finally able to reveal #macroservices. More details at macroservices.org
20
75
10
233
"This avoids the problem of large monoliths that grow constantly and eventually become unmaintainable." - Sad to hear that static code analysis tools that have been developed to fight exactly this problem (e.g. @sonargraph and others) seem still not to be in wide-spread use...
1
1
Replying to @i_kellner @sonargraph
Even when they’re used, they’re not a magic cure. They make the problems more visible, earlier, but they’re not a solution to those problems

May 11, 2020 · 9:28 AM UTC

3
1
Replying to @stilkov @i_kellner @sonargraph
I dare to disagree - they can be en excellent solution if used appropriately. Devs will know immediately when they break architectural boundaries. /1
1
I’m not disputing the value of those tools. What I’m saying is: They surface the problems, but they don’t solve them. You still have to do that in some other way.
2
1
more replies
Replying to @stilkov @i_kellner @sonargraph
A monolith based on DDD with an enforced architectural model avoids many of the problems we only have because we refuse or are unable to do monoliths right. /2
1
2
Replying to @stilkov @sonargraph
Agreed! I would go as far as saying there is no magic cure. :-) Of course, there needs to be the willingness to fight the entropy that those tools reveal... A solution needs to be developed by humans, but tools can help.