I'm very new to Etherium. I have a dapp requirement to store 40 key / value pairs for each of our customers.
I was thinking to create a contract that had a mapping between addresses and an array of structs. The address keys being for each of our customers and the array of structures storing key value pairs.
The data will be frequently read and infrequently updated.
When updates occur they will be done by the customers, either adding a new keypair or modifying / deleting an exisiting one.
There could potentially be hundreds of thousands of customers.
My question is, would this be a suitable data structure?
Specifically, would the gas fee payable by a customer to update a key / value pair increase with the number of customers / records stored?
If the answer to that question is yes and the structure is prohibitive, is there another suggested pattern I should look into?
This post is similar however I didn't see a clear answer for this specific question.
Thanks very much for your help! :-)
