3 ms·
> the database is enormous and constantly changing, so it's probably impractical to have development copies that are sufficient to test your code against realis
by random42 16y ago
> the database is enormous and constantly changing, so it's probably impractical to have development copies that are sufficient to test your code against realistically
What the hell? why not?
- clojurerocks 16y agoConsidering they use mysql how feasible is it for the database to be constantly changing? I think ive read that they use it more as a key value store then a relational store but still.
- kingnothing 16y agoAs far as I know, Facebook uses Cassandra not MySQL.
- random42 16y agoFor development/testing purpose, updated schema is enough; up-to-date data is not required.
- skybrian 16y agoThat's sufficient for some kinds of testing. It's not sufficient for performance testing or testing for changes in user behavior.
- random42 16y agoI don't know. We use artificially populated data for performance testing. for user behaviour and other metrics, they would have programs running against the actual production database, not a stale developer copy of it.
- modoc 16y agoAgreed. Every large company I've worked with has had scripts that create sanitized versions of the production DB, with PCI and PII stripped out or masked to allow for testing against full size datasets. It's not hard to do.