Re:Sample cloud-native application with microservices
by lilcorey10 on Friday February 15, 2019 @12:07AM
(#19168578)
Architecting microservices like your org chart would be Conway's Law, correct?
Re:Sample cloud-native application with microservices
by dllthomas on Friday February 15, 2019 @12:12AM
(#19168594)
Yeah, I don't think it's "reverse" either.
The common quote "if you have four groups working on a compiler, you’ll get a four-pass compiler" clearly has architecture following from organizational structure.
Re:Sample cloud-native application with microservices
by majewsky on Friday February 15, 2019 @06:58AM
(#19170156)
It's reverse because Conway's Law, as stated, says that code structure inadvertently arises from org structure, i.e. code = f(org). The reversal is to architect the org structure to ensure optimal code structure, i.e. org = f(code).
Re:Sample cloud-native application with microservices
by dllthomas on Friday February 15, 2019 @11:54AM
(#19172437)
That is reverse, yes.
I think your original comment was unclear, if not misstated. I had read the "like" in "[a]rchitect your microservices like your org chart" as something like "to resemble", and the rest of the comment seems to follow just fine. Other readings seem possible but I don't see one that gives the sense you want without what feels like some serious contortion.
In any case, no worries, we're clearly on the same page now - just trying to figure out what went wrong.
One of the main benefits of decoupling a monolithic application is getting the freedom to release, scale and manage different components separately. Each team becomes empowered to define their own practices, procedures and policies that are appropriate to their business requirements.
Have a mission-critical component that needs 5 9s reliability (auth or billing)? Great, release that carefully over multiple days with canarying across failure zones. Working on an experimental API for a new mobile app? Awesome, ship every commit.