Tim Bray was always an architecture astronaut, but this example of cloud services for a toy shopping cart app points to an overengineering pathology in our industry. Complexity bloat is real and it has made the cloud fairly noxious. https://www.tbray.org/ongoing/When/202x/2020/08/09/Service-Fabric-News …
-
-
Which, to be fair, will happen if my bid for Pinterest is accepted.
Show this thread -
Since a lot of the unnecessary complexity is introduced by fearsomely smart people at Google and Amazon, there's a stigma against calling it out. Maybe I'm just too dim to understand a 'services mesh'. But we saw this movie before, with SOAP and the "Semantic Web" and RDF and...
Show this thread
End of conversation
New conversation -
-
-
That's "predictable device names", to avoid the awkward situation where adding a network card will cause all of the names to shuffle around. While change is always annoying, I don't miss having eth0 suddenly be a different adapter after a reboot.
-
Yeah, all of the stuff individually has a rationale. Like my hardware raid card has options for grouping and so on that make sense if you have to manage hundreds of drives. The problem is when there's no option to keep things simple and usable (like mdadm in the RAID analogy)
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.