Notes on Theory of Distributed Systems [pdf]
Is anyone teaching &quot;Practice of boring Distributed Systems 101 for dummies on a budget with a tight schedule&quot; ?<p>As in, &quot;we have a PHP monolith used by all of 12 people in the accounting department, and for some reason we&#x27;ve been tasked with making it run on multiple machines (&quot;for redundancy&quot; or something) by next month.<p>The original developpers left to start a Bitcoin scam.<p>Some exec read about the &quot;cloud&quot;, but we&#x27;ll probably get just enough budget to buy a coffee to an AWS salesman.<p>Don&#x27;t even dream of hiring a &quot;DevOps&quot; to deploy a kubernetes cluster to orchestrate anything. Don&#x27;t dream of hiring anyone, actually. Or, paying anything, for that matter.<p>You had one machine ; here is a second machine. That&#x27;s a 100% increase in your budget, now go get us some value with that !<p>And don&#x27;t come back in three months to ask for another budget to &#x27;upgrade&#x27;.&quot;<p>Where would someone start ?<p>(EDIT: To clarify, this is a tongue in cheek hyperbole scenario, not a cry for immediate help. Thanks to all who offered help ;)<p>Yet, I&#x27;m curious about any resource on how to attack such problems, because I can only find material on how to handle large scale multi million users high availability stuff.)