http://simonwillison.net/2020-05-11T19:11:47+00:00Simon Willison2020-05-11T19:11:47+00:002020-05-11T19:11:47+00:00https://simonwillison.net/2020/May/11/why-we-famous_company-switched-hyped_technology/#atom-tag

<p><strong><a href="https://saagarjha.com/blog/2020/05/10/why-we-at-famous-company-switched-to-hyped-technology/">Why we at $FAMOUS_COMPANY Switched to $HYPED_TECHNOLOGY</a></strong></p> Beautiful piece of writing by Saagar Jha. “Ultimately, however, our decision to switch was driven by our difficulty in hiring new talent for $UNREMARKABLE_LANGUAGE, despite it being taught in dozens of universities across the United States. Our blog posts on $PRACTICAL_OPEN_SOURCE_FRAMEWORK seemed to get fewer upvotes when posted on Reddit as well, cementing our conviction that our technology stack was now legacy code.” <p><small></small>Via <a href="https://news.ycombinator.com/item?id=23144380">Hacker News</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/migration">migration</a></p>

2018-06-27T15:05:36+00:002018-06-27T15:05:36+00:00https://simonwillison.net/2018/Jun/27/migrating-messenger-storage-optimize-performance/#atom-tag

<p><strong><a href="https://code.facebook.com/posts/201318390519340">Migrating Messenger storage to optimize performance</a></strong></p> Fascinating case-study of a truly gargantuan migration. Messenger has over a billion users, and Facebook successfully migrated its backend storage from HBase to their MyRocks database (a fork of MySQL with a storage engine built on their SSD-optimized RocksDB key/value library) without any user-visible downtime. They ended up using two migration paths: one for the 99.9% of regular accounts, and a separate path for extremely high volume accounts (businesses with very active chat bots or support systems). <p><small></small>Via <a href="https://news.ycombinator.com/item?id=17402241">Hacker News</a></small></p> <p>Tags: <a href="https://simonwillison.net/tags/facebook">facebook</a>, <a href="https://simonwillison.net/tags/migration">migration</a>, <a href="https://simonwillison.net/tags/mysql">mysql</a>, <a href="https://simonwillison.net/tags/scaling">scaling</a>, <a href="https://simonwillison.net/tags/zero-downtime">zero-downtime</a></p>

2007-11-23T23:49:10+00:002007-11-23T23:49:10+00:00https://simonwillison.net/2007/Nov/23/evolution/#atom-tag

<p><strong><a href="http://code.google.com/p/django-evolution/">Django Evolution</a></strong></p> Really smart take on the problem of updating database tables to reflect changes to Django models. Code that automatically modifies your database tables can be pretty scary, but Evolution seems to hit the right balance. <p>Tags: <a href="https://simonwillison.net/tags/databases">databases</a>, <a href="https://simonwillison.net/tags/django">django</a>, <a href="https://simonwillison.net/tags/djangoevolution">djangoevolution</a>, <a href="https://simonwillison.net/tags/migration">migration</a>, <a href="https://simonwillison.net/tags/orm">orm</a>, <a href="https://simonwillison.net/tags/schema">schema</a></p>