Database for books?

Question

SQL

Essence: The DB in which books will be stored is planned. Chapters are the basic unit of information. Chapters can be from a couple of sentences to a couple of hundred.
Question: How best to organize storage with this approach and what technology to choose. Will any base work? Or maybe there are specialized tools for such things?
UPD:The stack of operations is standard. Adding a chapter to the database, reading from the database. Formation of the book (fb2, epub), after the final chapter. Books do not interact with each other. Authors and other tags are not that important. I am more confused by the volume of chapters and books in general. There aren't any limits. Each work can contain 100,500 chapters, and those, in turn, have the same number of characters. We need tools, or methods, how to organize it all, so that, if possible, not to inflate the database, not to lose performance and speed.

Answer 1

FK
M2M
EAV
when all three abbreviations are clear - your question is solved automatically