C
Coding the Architecture
codingthearchitecture.com · Group blog · on HN since 2010
Simon Brown writes about software architecture, including modular monoliths, documentation, and how to visualize and structure systems.
What HN saysHN commenters cite it for Simon Brown's modular monoliths talk, linking it in discussions of microservices and cohesion.
15HN people shared it
3linked it in comments
16stories submitted
83story points
4 years agolast shared
2010people per year2026
Most-shared posts
- 1Distributed big balls of mud (2014)4 people · 51 points · first shared 2014 · 22 comments on HN
- 2Today's software developers are the ivory tower architects of tomorrow2 people · 4 points · first shared 2018 · 1 comments on HN
- 3Software documentation as a guidebook1 people · 11 points · first shared 2013 · 3 comments on HN
- 4PaaS for Java Developers: Coding the Architecture1 people · 3 points · first shared 2017 · 1 comments on HN
- 5Modular Monoliths – Coding the Architecture1 people · 2 points · first shared 2016 · discussion on HN
- 6Where are the software architects of tomorrow?1 people · 2 points · first shared 2011 · discussion on HN
- 7Architectural constructs1 people · 2 points · first shared 2010 · discussion on HN
- 8Visualising and documenting software architecture cheat sheets1 people · 2 points · first shared 2017 · discussion on HN
- 9Layers, Hexagons, Features and Components1 people · 2 points · first shared 2019 · discussion on HN
- 10Introducing Structurizr1 people · 1 points · first shared 2015 · discussion on HN
- 11Collaborative Design1 people · 1 points · first shared 2011 · discussion on HN
- 12Jitter - The forgotten performance metric1 people · 1 points · first shared 2011 · discussion on HN
- 13Software Architecture for Developers - v1 of the book is published1 people · 1 points · first shared 2012 · discussion on HN
- 14Package by component and architecturally aligned testing1 people · first shared 2017
- 15Sa2015 modular monoliths1 people · first shared 2016
What HN people wrote when they linked it
pieterh_pvtl · 2016-09-15
There is a great talk on this by Simon Brown
http://www.codingthearchitecture.com/presentations/sa2015-modular-mono…
https://www.youtube.com/watch?v=h_rBDIC51C4
ChrisCinelli · 2022-05-10
Microservices are not to scale organization even if some organizations used them in this way. There is a big problem with this way of scaling. The sense ownership becomes the sense of defend your castle (team's microservice code) from invasion (external developer that are trying to add features or fix bugs).
Microservices were also presented as a solution for encapsulation. But if you cannot write good encapsulated code in a monolith, what makes you think microservices are the answer? http://www.codingthearchitecture.com/2014/07/06/distributed_big_balls_…
Microservices (or just services) are the solution of having more bandwidth for a set of features without having to more of everything else and preventing some part of the code to influence negatively some others.
gumoro · 2017-07-05
Higher cohesion and modularity.
I'm glad to see this in an article for JavaScript projects. Here are a few articles for Java projects, that go in more details (I think the concepts still mostly apply to JavaScript projects):
http://www.javapractices.com/topic/TopicAction.do?Id=205
http://www.codingthearchitecture.com/2015/03/08/package_by_component_a…