<story><title>Apply Unix Principles to Write Testable Microservices</title><url>https://microservices-on-my-mind.blogspot.com/2019/04/break-functional-and-orchestration.html?m=1</url></story><parent_chain></parent_chain><comment><author>gambler</author><text>In 1997 at OOPSLA Alan Kay said &amp;quot;every object on the internet should have a URL&amp;quot;. The response at that time (and many years afterward) could be generally described as smugnorant mockery. A bunch of smart-asses decided that &amp;quot;it doesn&amp;#x27;t work&amp;quot;, mostly by sharing gossip about CORBA failures, rather than looking into relevant research and experiments.&lt;p&gt;20+ years later we get the same idea presented as some groundbreaking revelation, except it&amp;#x27;s made orders of magnitude more complicated by the virtue of being an ad-hoc accretion of &amp;quot;hip&amp;quot; technologies. All created with zero overarching vision by people who clearly aren&amp;#x27;t even aware of past research or ideas. The crowds applaud - themselves.&lt;p&gt;This is depressing.</text></comment>
<story><title>Apply Unix Principles to Write Testable Microservices</title><url>https://microservices-on-my-mind.blogspot.com/2019/04/break-functional-and-orchestration.html?m=1</url></story><parent_chain></parent_chain><comment><author>itamarst</author><text>Microservices are an organizational pattern: &amp;quot;we have 500 programmers working on one application, how the hell do we do it.&amp;quot;&lt;p&gt;Solution: break up application into independent projects, each team of developers works on one of them, have extra team that builds tooling to make everyone happy.&lt;p&gt;Using microservices with a small teams is a terrible idea, usually, because you&amp;#x27;re switching to a distributed system when you don&amp;#x27;t need to. And distributed systems are hard to get right. And you&amp;#x27;re not even following the organizational pattern, because you have one team with N microservices.</text></comment>