Dropbox’s Exodus from the Amazon Cloud

Re:Dropbox’s Exodus from the Amazon Cloud by jamwt on Monday March 14, 2016 @01:22PM (#11284069)

We use 3rd parties for the "obvious" stuff. Like, we're not going to reinvent json serialization. But we typically don't use any 3rd party frameworks on the backend. So things like service management/discovery, rpc, error handling, monitoring, metadata storage, etc etc, are a big in-house stack.

So, we use quite a few crates for the things it makes no sense to specialize in Dropbox-specific ways.

[ Parent | on HN ]

Re:Dropbox’s Exodus from the Amazon Cloud by dikaiosune on Monday March 14, 2016 @01:32PM (#11284132)

Cool. This might be getting into the weeds a bit, but are you still on rustc-serialize for json or are you trying to keep up with serde/serde_json? If you're using serde, are you on nightly? From your comment above I got the impression that only using stable features was very important, so I'm curious how your codebase implements/derives the serde traits.

[ Parent | on HN ]

Re:Dropbox’s Exodus from the Amazon Cloud by jamwt on Monday March 14, 2016 @01:56PM (#11284310)

We're on rustc-serialize. JSON is not really a part of our data pipeline, just our metrics pipeline. So the performance of the library is not especially critical.

[ Parent | on HN ]