Some kinds of data lend themselves to being represented by many small records. For example, my current client needs a list of companies, where each company is just a short string name. Each name should be unique so it would make sense to create a model. Unfortunately there will be several hundred companies, so modelling it this way would hit the limit on records and require paying for the professional plan.
Instead I’ve modelled the list of companies as a singleton entity with a modular content field, and a Company block. I’ve had to do without unique-name validation. Presumably it wouldn’t actually cost Dato any more to store this data as records rather than blocks?
I feel that this is against the spirit of the developer plan! An app may store a small volume of data in terms of KB, rarely update or query it (because the app has few users), and yet need to pay €1800 per year because the data happens to be split across many small records.
It would be great if the developer plad had some allowance for many small records. For example, making the limit “300 records or 300 KB of record data, whichever is greater”.