I have begun using PlanetScale to work with a REST API, and I've been advised that noSQL is a better choice than SQL for REST APIs. I'm now wondering if it's better to store all the data in a single JSON column or split it up into different tables. Although the JSON approach may consume more
developer echat storage space and lose the SQL's strictness, I'm also concerned about the read/write burden of splitting the data into multiple tables. I would appreciate
koows any suggestions on the most optimal solution.