I have a data structure, a large dictionary, that is mutated by several functions. Each function does a database call, some calculations and then changes the value of a key in the data structure. Each function never changes more than 2 keys in the dictionary with the vast majority of functions changing only one.
I've encapsulated all this code in a class but I'm at a loss as to what to call it. I thought about going with Strategy but my colleague rightly pointed that there's never more than one implementation of that class.
Is there even an applicable design pattern?