81–87 of 87 posts
Earlier quoted context omitted.
Why would a single deployment unit have to be written in exactly one language?
OK, count me onboard! Can we convince the 2-3 other stakeholders in our deployment unit to go with this crazy plan? Or are there 40-60 other stakeholders we need to convince?
This is basically Conway's Law in practice: microservices aren't created because of technical boundaries, but they emerge because organizations need team boundaries. https://en.wikipedia.org/wiki/Conway%27s_law
Less-competent devs and CTOs hear that Amazon & Google use it, then decide their 12-person team needs to rewrite their product as 5 separate services. I have encountered companies with 50 services where they needed 5, spending 60% of their dev velocity on overhead.
If you're contemplating microservices & haven't already nailed your business transaction boundaries, reliability mechanisms, idempotence, deployment management/ versioning, observability, testability and the operational discipline to run distributed systems you should just stop -- you have no freaking clue and you're going the wrong way.
Earlier quoted context omitted.
Yes, and then they start complaining that the shared domain objects are not kept up to date by team $notMine, and so they inevitably go to a shared library where they fall back into the same issues.
Is that a result of poor DDD, not modelling more appropriate objects? Eg a Customer Address, Delivery Address, Invoice Address Vs just a single shared Address Or is there still too much conflict for the truly shareable objects?
Earlier quoted context omitted.
Is that a result of poor DDD, not modelling more appropriate objects? Eg a Customer Address, Delivery Address, Invoice Address Vs just a single shared Address Or is there still too much conflict for the truly shareable objects?
It's a result of being human, and the fact that we still haven't figured out how to work together well.
It's really tiring trying to engage in curious discussion on HN. Seems people just want to make attempts at witty remarks and talk past people
This is basically Conway's Law in practice: microservices aren't created because of technical boundaries, but they emerge because organizations need team boundaries. https://en.wikipedia.org/wiki/Conway%27s_law
e.g., there's a reason that fancy buildings have maintenance hatches for humans
[flagged]
I have a team that doesn't communicate well and is generally dysfunctional in all ways imaginable. Microservices isolate them quite literally and lets them work in peace and quiet. The system as a whole is completely batshit crazy of course, but for some teams, this can turn an unworkable situation into "we might survive this" which is when push comes to shove all that matters.
It's far better to have systems in place that fail with culture this broken than one that enables it to limp along.