News for hackers. Stuff that matters.
Re:Ask HN: Is there a better way to document complex softwar... by basdp on Sunday November 25, 2018 @03:05PM (#18528709)
All the time.
Re:Ask HN: Is there a better way to document complex softwar... by mden on Sunday November 25, 2018 @06:25PM (#18529750)
My initial impression is the same as the parent. Juxtaposing microservices and KISS seems weird as the "architectural complexity" of microservices is several times higher than a monolith. You're not only multiplying the points of failure but also increasing the difficulty of translating the domain into code, especially when it comes to reading and writing from a db in a safe and efficient manner. Someone will need to come up with an answer to handling transactional operations that span multiple services sooner or later (or I guess the team can just accept some small percent of data corruption, which is what I'm guessing most companies that do microservices actually do, willingly or unwillingly). Ironically I think the benefit of an architect is a lot more evident in a microservice architecture than a monolith.

Edit: though maybe my view on what an architect should do is different? I think of a software architect as the person that lays out the skeleton and foundations of a project and has the answers to hard questions. Very likely someone who actively codes or has solved very similar challenges to the ones being solved.

Re:Ask HN: Is there a better way to document complex softwar... by basdp on Monday November 26, 2018 @07:58AM (#18532977)
The problem with this approach is that it might be easier to build a monolith, maintaining it and the ops side of it is far more complex.