I need a sort of term database with around 3 fields that won't be used during normal site operations.. Only when I, the administrator, add content.
I'm wondering about how to minimise performance impact for regular users.. My intuition tells me that a field collection would be better so the nodes table is smaller.
I will be likely be using some code to add data from APIs and Rules to fetch the data by property.
Which should i use? I don't have much interest in creating a custom entity type unless it's really easy.. I want image and audio fields and I don't know if that complicates things.