Many-to-many database

I am thinking about making a music database. Something where you can search by artist, album or song. This seems to be a Many-to-many model, as an album can have multiple songs, and the same song can be on different albums. Currently I am just using some JSON files, but this isnt really robust, as it can only represent hierarchical data. This would just be a personal project, so I dont need anything too involved. I have looked at SQLite, but also Document-oriented databases. I like the idea of being able to persist the data as JSON or CSV files. What is a good option for my use case? --- Response to some questions: > Do you want a free solution or need to use an enterprise level system like > Microsoft SQL Server which costs money. Free options only > How far do you expect to scale your database?...in other words, in the > foreseeable future roughly how big do you expect it to get (data-wise), how > many users do you expect will be using it both overall and at a given instance > of time, how often will data change inside of it? Most likely it would be a tool that only has one user at a time. So either I would use it myself, or someone might download my tool and use it for themselves. > What does your current technology stack look like? I would prefer something with of of these if possible: C#, D, Go, Nim or Rust. Although I have seen many options in C and C++, so I might have to end up with one of those. > I don't think any modern solution out there persists the underlying data of > the database in JSON or CSV files (though I could be mistaken). I think Document-oriented database offer this, but I could be misunderstaning it. Also I had seen Export to CSV for SQLite.