YouTube System Design for Robotics Data Infrastructure

Very interesting thought experiment. One thing I'm curious is how you might think through scale, certain data formats scale much faster and may consume more space than others. How do balance both growth of data formats and overall how much data can be hosted?

What does YouTube system design have to do with robotics data?

When we started building Pareto, we weren’t thinking about YouTube, but the data path looked familiar: upload, process, store, index, play.

Here's what the classic system design question gets right in production.

- Read: https://hebbianrobotics.com/blog/youtube-system-design-for-r...

- Try Pareto: https://pareto.hebbianrobotics.com

- Code open source: https://github.com/Hebbian-Robotics/pareto