Should I use ORM to model a large tree structure?

We are developing a Video on demand system in which users can upload video. We want to create a tree-like structure of the archive of videos, where the user can create folders for artists / albums, etc. And save the video in the right folders. Like all tree structures, the user will be able to move video between folders, delete auxiliary trees, copy video, and move auxiliary trees and children.

A tree can contain 10,000,000 videos and folders.

My question is: is ORM suitable for a tree similar to a structure of this size?

+4
source share
1 answer

Assuming your tree structure in the database will be a table like:

FolderId | ParentFolderId | Foldername

Why not?

The question is not whether you should use ORM or not, the question is what problem do you have, that ORM is the right tool to solve.

+5
source

Source: https://habr.com/ru/post/1395743/


All Articles