What software engineers can learn from the rapid collapse of Fast

Re:What software engineers can learn from the rapid collapse... by lupire on Thursday April 07, 2022 @06:32PM (#30951116)

> The TailScale folks caught a bunch of flak for their "do things that don't scale" approach to databases.

I've seen this repeated on HN, but never saw the alleged flak.

[ Parent | on HN ]

Re:What software engineers can learn from the rapid collapse... by Aeolun on Thursday April 07, 2022 @08:53PM (#30952113)

It’s a post from around a week ago. They went from embedded JSON, to something else (equally crazy), to embedded JSON again. Lots of laughs were had (and a lot of, just use postgres).

[ Parent | on HN ]

Re:What software engineers can learn from the rapid collapse... by randomdata on Friday April 08, 2022 @01:11AM (#30953535)

> They went from embedded JSON, to something else (equally crazy), to embedded JSON again.

They went from a JSON file, to etcd, to SQLite. etcd seems a little misplaced, but presumably it was already in their infrastructure and they thought they could save time leveraging it. The file-based approach seems appropriate for their particular use-case, though. It's not like it's a Rails app.

[ Parent | on HN ]

Re:What software engineers can learn from the rapid collapse... by Aeolun on Friday April 08, 2022 @03:46AM (#30954385)

Crap, I’d forgotten about the sqlite part. You are of course correct. Apparently I’d only remembered the fact they went back to something file based :/

I’m still of the opinion that whatever you are storing, if your alternatives are JSON or Sqlite, etcd is a really strange/unconventional choice.

[ Parent | on HN ]