4 ms·

I dont get it, care to elaborate?

• yakshaving_jgt 4y ago
  I mean I don't agree with the analogy that the author has drawn between a micro-service architecture and UNIX programs piped together, because I don't believe inter-process communication through streams is comparable to HTTP requests over the internet. Put another [less accurate] way: a function call is not the same as a network request. The analogy the author has drawn in the article is a kind of mental model — an intentional oversimplification — intended to convey an idea. It's useful to use mental models like this, but only if you have sufficient understanding of the underlying mechanics that you're abstracting over in order to determine whether the abstraction is useful, or if it's harmful. In my opinion, because the underlying mechanics are so different, the mental model isn't actually useful. The author writes: > The idea can be applied to the web in a similar way. Many modern web applications are choosing to build out their architecture as a set of services that communicate over the network layer, which has some parallels with the Unix model of programs that communicate via OS primitives. I just don't agree with this. The author appropriately recognises that this kind of architecture often makes it considerably harder for us to manage shared context, but elides that other serious drawback that I've described.