you are viewing a single comment's thread.

view the rest of the comments →

[–]d3rr 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (6 children)

Well if their architecture is to store the DB inside of a git repo that's pretty bad design. But yes, they wipe the floor with us as they are decentralized.

[–]wizzwizz4 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (5 children)

Why is storing the database in a git repository bad design? Inefficient, yes, but Git has almost all of the features a good backup system needs.

[–]d3rr 1 insightful - 1 fun1 insightful - 0 fun2 insightful - 1 fun -  (4 children)

Because code is not data and vice versa. It's extra risk that sets you up for exactly what happened- switching branches replaced/reverted the DB data with something else. Ideally you can blow away the repo, re check out, DB data is happily in safe in /var or somewhere.

[–]wizzwizz4 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (3 children)

Wait. They were storing it in the same repository as the code? Oh, yeah, that's stupid.

[–]d3rr 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (2 children)

Yep, dude talked about it in his what happened post. Probably in there but ignored by git, since they didn't have a backup.

[–]wizzwizz4 3 insightful - 1 fun3 insightful - 0 fun4 insightful - 1 fun -  (1 child)

Ah. Then that's just a mistake. An easy one to make, actually, if you don't know how git works.

[–]d3rr 2 insightful - 1 fun2 insightful - 0 fun3 insightful - 1 fun -  (0 children)

Agreed, but still bad design/setup to store the data there.