

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 3
click for more info
Not enough gems
Cost: 6 gems
1: Welcome
incomplete
2: Large Files
incomplete
3: Database
incomplete
4: Videos
incomplete
5: Multipart Uploads
incomplete
6: Encoding
incomplete
7: Using the Filesystem
incomplete
8: Mime Types
incomplete
9: Live Edits
incomplete
This lesson's interactive features are locked, please to keep using them
With Tubely, we have it easy. Users won't be able to make small tweaks to existing images and videos - like changing the background color or adding a text overlay.
We'll force them to simply upload new versions of the file (even YouTube has this restriction, even with their resources).
If a user were able to live edit a file (think Google Docs or Canva) we'd have to approach our storage problem differently. We wouldn't just be managing new versions of "static" files, we would need to handle every tiny edit (keystroke) and sync updated changes to our server. That's much more complicated and outside the scope of this course.
Luckily, those requirements are also less common in the real world. The Tubely use case (storing and serving entire assets) is much more common and much easier to implement.