loading...

Discussion on: Organic Software Architecture

Collapse
jamesmh profile image
James Hickey

I feel like each point should be a post on it's own! All very important issues.

I think out of everything here (a fantastic post), I'd like this elaborated on more:

Changing the technical solution won't do anything if the backbones of organizational structures remain as they are.

Collapse
kmruiz profile image
Kevin Mas Ruiz Author

Hi James! thanks for your feedback! I will try to elaborate more on each topic with new posts 😊😊 and this one will be next in line.

As a summary, in my experience, I've found that just changing the structure of the software we deliver (for example, from a monolith to microservices with event sourcing) doesn't provide any meaningful value if we, as an organization, do not change how we understand value delivery.

If your practices lead you to have a coupled monolithic organization, even if you invest tons of money to fix it, if you don't change those practices you will eventually go back to the situation with a monolithic architecture (or even worse, with a microservices architecture that is highly coupled, which is more expensive).

Collapse
tonyhicks20 profile image
Tony Hicks

Have you ever heard of Conway's law? From Wikipedia : Conway's law is an adage stating that organizations design systems which mirror their own communication structure.

Collapse
kmruiz profile image
Kevin Mas Ruiz Author

Yes! It's amazing! Most of my work is inspired by the Conway's Law, Chaos Engineering and Lean and Agile Methodologies.