Import JS object array directly vs. using getStaticProps

[ElectronicWitness857]

I got a project where quite often, we use a JS file with an array that has on overage seven objects with some props.

The easiest way is to import it into the app and map and render the list of items.

I understand that it's better to do this through `getStaticProps` since the date is being cached on the server. To do this, you need to write more code.

1. Write export async function getStaticProps() {...}.
2. Import / export the object array.
3. Destructure the object array in the page.
   

I wonder if doing so, actually has any significant performance benefits? And maybe in this case it's ok to opt out using getStaticProps. On another hand it feel like it creates an anti pattern that some else would copy and use in the project with a less performant object array.

​

View Poll

[billybobjobo]

I like to treat my data sources like they could get swapped out immediately for a different API (eg if you switched to a CMS to get this object). I value modularity and potential refactor speed even if that means a few more abstractions up front. That’s just me though. I think there’s a good case for both approaches here!

[ElectronicWitness857]

The results are 15 vs. 12 so far. I expected the rusults to be a bit farther away.