I found this article interesting and enjoyable, but I had some questions about this: Let’s apply this to our software systems. Instead of building a monolithic

I found this article interesting and enjoyable, but I had some questions about this: Let’s apply this to our software systems. Instead of building a monolithic 100 000 line codebase, build 100 small services, each 100 lines long. Fred George, (the inventor of programmer anarchy) one of the biggest proponents of this approach, calls these small programs micro-services. a.) With this sort of system, how do you avoid a sort of high level version of spaghetti code (spaghetti services), where services depend on each other willy nilly, and b.) where if one service goes down, it brings other large chunks of the system down. c.) Finally, any concern that a bunch of services communicating with each other over http might be substantially slower than a monolithic system largely communicating with itself in memory?