Monoliths are not dinosaurs
allthingsdistributed.com
Monoliths are not dinosaurs
1–10 of 243 posts
Re: Monoliths are not dinosaurs
#2Added to https://www.microservice-stories.com - thanks!
Re: Monoliths are not dinosaurs
#3Added to https://www.microservice-stories.com - thanks!
Bookmarked; thanks for that link. Bonus points for sentiment analysis.
Re: Monoliths are not dinosaurs
#4Werner's advice in my own words:
1. Don't pick an architecture because it's all the rage right now.
2. Don't pick an architecture that mimics your org's structure. Aka don't fall prey to Conway's law: https://en.wikipedia.org/wiki/Conway%27s_law.
3. Don't pick an architecture that your team can't operationalize--e.g. due to lack of skills or due to business constraints.
Re: Monoliths are not dinosaurs
#5Can't we all just go back? Seriously every system I've worked on in the last 10 years seems worse in every metric than what I worked on 2000-2010.
Re: Monoliths are not dinosaurs
#6Werner's advice in my own words: 1. Don't pick an architecture because it's all the rage right now. 2. Don't pick an architecture that mimics your org's structure. Aka don't fall prey to Conway's law: https://en.wikipedia.org/wiki/Conway%27s_law . 3. Don't pick an architecture that your team can't operationalize--e.g. due to lack of skills or due to business constraints.
(Some of) Werner's advice in his own words (from the linked article):
* "I always urge builders to consider the evolution of their systems over time and make sure the foundation is such that you can change and expand them with the minimum number of dependencies."
* "There are few one-way doors. Evaluating your systems regularly is as important, if not more so, than building them in the first place."
Re: Monoliths are not dinosaurs
#7[dead]
Re: Monoliths are not dinosaurs
#8Werner's advice in my own words: 1. Don't pick an architecture because it's all the rage right now. 2. Don't pick an architecture that mimics your org's structure. Aka don't fall prey to Conway's law: https://en.wikipedia.org/wiki/Conway%27s_law . 3. Don't pick an architecture that your team can't operationalize--e.g. due to lack of skills or due to business constraints.
> Aka don't fall prey to Conway's law
You can't not fall prey to Conway's law. You can only choose how you organize your people and their interfaces.
Re: Monoliths are not dinosaurs
#9Werner's advice in my own words: 1. Don't pick an architecture because it's all the rage right now. 2. Don't pick an architecture that mimics your org's structure. Aka don't fall prey to Conway's law: https://en.wikipedia.org/wiki/Conway%27s_law . 3. Don't pick an architecture that your team can't operationalize--e.g. due to lack of skills or due to business constraints.
> Aka don't fall prey to Conway's law You can't not fall prey to Conway's law. You can only choose how you organize your people and their interfaces.
Right! Decide on the shape of the software, then rearrange your organization to match.
Re: Monoliths are not dinosaurs
#10Werner's advice in my own words: 1. Don't pick an architecture because it's all the rage right now. 2. Don't pick an architecture that mimics your org's structure. Aka don't fall prey to Conway's law: https://en.wikipedia.org/wiki/Conway%27s_law . 3. Don't pick an architecture that your team can't operationalize--e.g. due to lack of skills or due to business constraints.
> Aka don't fall prey to Conway's law You can't not fall prey to Conway's law. You can only choose how you organize your people and their interfaces.
Org will be orgs… and I find it hard to disagree with you :(
The only counterexample to Conway that I have seen working is “away teams”:
https://pedrodelgallego.github.io/blog/amazon/operating-mode...