News for hackers. Stuff that matters.
Re:Systems design explains the world: volume 1 by tome on Sunday December 27, 2020 @04:55PM (#25554589)
> 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.

Re:Systems design explains the world: volume 1 by apenwarr on Sunday December 27, 2020 @05:01PM (#25554635)
Kubernetes is the biggest and worst second system effect I’ve seen in years.
Re:Systems design explains the world: volume 1 by qznc on Monday December 28, 2020 @06:52AM (#25558510)
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/goog...

Re:Systems design explains the world: volume 1 by l0b0 on Sunday December 27, 2020 @05:42PM (#25554901)
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.
Re:Systems design explains the world: volume 1 by glogla on Sunday December 27, 2020 @06:07PM (#25555040)
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.