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
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
3
1
I dare to disagree - they can be en excellent solution if used appropriately. Devs will know immediately when they break architectural boundaries. /1
1
Replying to @AZ_hello2morrow @i_kellner @sonargraph
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.

May 11, 2020 · 6:35 PM UTC

2
1
Replying to @stilkov @i_kellner @sonargraph
You are right in the sense that we still need a human brain to solve the issues. But knowing is half the battle. The big ball of mud is created by not being able to see the bigger picture when it comes to architecture and dependencies. /1
1
1
Replying to @stilkov @i_kellner
Automation is key. Tools like @ArchUnit and @Sonargraph break the build if rules are violated. You still need a good model and that can be hard to get it right. At the end it is all a trade-off where we need to get our priorities right. /2
1
1