4 ms·

> 1. Nobody is doing rewrites from scratch anymore. That's just not the case. This claim would be more compelling if it provided a few notable examples.

• apenwarr 6y ago
  Kubernetes is the biggest and worst second system effect I’ve seen in years.
  • qznc 6y ago
    Is it an instance of the Second System Effect if you build something slightly different? Google is replacing its internal systems all the time. For example, MapReduce was replaced with Cloud Dataflow [0]. [0] https://www.datacenterknowledge.com/archives/2014/06/25/google-dumps-mapreduce-favor-new-hyper-scale-analytics-system/ https://www.datacenterknowledge.com/archives/2014/06/25/goog...
• l0b0 6y ago
  I worked on one rewrite of an old system which I can't really talk about, but which was very successful (the only thing we kept was the data). I also remember reading many years ago that every major version of Windows is essentially a rewrite from scratch.
• glogla 6y ago
  We just deployed rewrite of Hadoop (sqoop, hive, ...)/Teradata based Data Lake & Data Warehouse to Cloud based Serverless Lakehouse with Spark as the main workhorse. This included migrating about 1/2 petabyte of old data and rebuilding several Kimball-style Data Marts to Data Vault approach, which pairs really well with the Lakehouse-style tech stack. This all took about 9 months, which is a long time, but it was in highly regulated industry where compliance, security and data integrity get a lot of scrutiny. In the end, nothing of the previous solution survived - no code and no infrastructure.