<story><title>Scaling One Million Checkboxes to 650M checks</title><url>https://eieio.games/essays/scaling-one-million-checkboxes/</url></story><parent_chain></parent_chain><comment><author>pizzafeelsright</author><text>Many lessons learned along with great historical knowledge of (distributed) systems.&lt;p&gt;I think you hit every type of interruption and point of failure, except storage space, and it is great to see your resolutions.&lt;p&gt;I wasn&amp;#x27;t aware Redis could do the Lua stuff which makes me very interested in using it as an alternative state.&lt;p&gt;As for the bandwidth - one of my biggest gripes with cloud services as there is no hard limit to avoid billing overages.</text></comment>
<story><title>Scaling One Million Checkboxes to 650M checks</title><url>https://eieio.games/essays/scaling-one-million-checkboxes/</url></story><parent_chain></parent_chain><comment><author>xnx</author><text>&amp;gt; Building the site in two days with little regard for scale was a good choice.&lt;p&gt;Probably the key takeaway that many early-career engineers need to learn. Scaling&amp;#x27;s not a problem until it&amp;#x27;s a problem. At that point, it&amp;#x27;s a good problem t have, and it&amp;#x27;s not as hard to fix as you might think anyway.</text></comment>