2 ms·
> I'd have first deployed existing, native code along with > Rust in parallel using the data splitting technique so > some is saved with original and some
by kibwen 11y ago
> I'd have first deployed existing, native code along with
> Rust in parallel using the data splitting technique so
> some is saved with original and some with Rust.
Yes, this is how Dropbox tests all of their features, and they did this with their new Rust-based storage engine as well. This tool has been in development for over a year by now and has seen extensive multi-stage testing (at first handling only a few terabytes of data, then "just" petabytes, and now exabytes).
- nickpsecurity 11y agoI was expecting they probably did given what's on the line. Re-reading it, I realize it probably didn't come off that way. Gotta work on that. Thanks for the confirmation, though. I do look forward to reading the experience report. Hoping they include data on all key attributes vs prior language: productivity, debugging time comparison, CPU use, memory use, integration issues, and any changes in defect rates. Community evaluating Rust needs that data for something at this level.