Thats a poor comprison — Monkeys only know how to shakespeare. For an example of unified effort " Netflix " microservices is a better comparison , and beats " Fornite " in terms of skill and craftmanship. 700 micro services all working with minimal latency , and load times.
-
-
I'd modify that wording slightly - it's to work /within/ Conway's Law. I've seen it mostly-successfully used at one org, where the repartitioning of teams and services were both equally viable if a business case could be made for doing so, included technical issues.
-
Basically, since Conway's Law will always take effect, don't fight it, but rather roll with it. But naively locking down the org structure while allowing services to be spun out willy-nilly is a recipe for disaster: ownership and unified priorities per team is necessary.
- Show replies
New conversation -
-
-
Have you explained this anywhere? I'd be interested in your perspective on microservices.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Not really. Right now we are at the stage where one developer craps out 7-8 microservices per month.
-
Yes. This is just Conway's Law in the developer's brain, which itself is segmented and unable to harmonize different things it has been taught. Conway's Law holds even inside a single developer's (poorly integrated) brain.
End of conversation
New conversation -
-
-
Would like to know what are the good reasons? Failure handling?
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The biggest problem with 'microservices' is doing it well takes a disproportionate amount of effort and maintenance over just making your code run faster. So people just do it badly and we end up with 500ms response times that have to be hidden behind async React bullshit.
-
When your fast code is in a monolith, you can’t run faster. Because you end up coordinating 15 teams to do a release in a worse case scenario (same case scenario for bad microservices). It’s not all black and white, it’s all shades of gray and blotches of color here and there.
- Show replies
New conversation -
-
-
I think this is the bane of companies above a certain size (above 150-200 people?). Up to that size a lot of stuff is built aroun dbusiness needs and domains. Finances here, streaming there, etc. Then disaster strikes: 1/
-
Now you have finance split into consumption, subscriptions, payments, payouts, and third-party integrations. You have streaming split into an increasing number of teams. And so on. And now you have Conway’s law in full swing, and a gazillion microservices to reflect that 2/2
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.