Memory Management & Garbage Collection

What memory management best practice should be applied to this class?

class ResourceManager {
  constructor() {
    this.resources = new Map();
  }
  register(id, resource) {
    this.resources.set(id, resource);
  }
  unregister(id) {
    this.resources.delete(id);
  }
  getResource(id) {
    return this.resources.get(id);
  }
}

Use WeakMap instead of Map if resource lifecycle is independent of registration
The best memory management practice for this class would be using WeakMap: 1) If the resources have lifecycles independent of their registration, a WeakMap prevents memory leaks, 2) A WeakMap would allow resources to be garbage collected when they're no longer referenced elsewhere, 3) With the current Map implementation, resources remain in memory even if they're no longer used outside the ResourceManager, 4) Using WeakMap eliminates the need for explicit unregister calls in many cases, 5) This is particularly valuable if clients might forget to call unregister, 6) The tradeoff is that WeakMap keys must be objects, not primitive values like strings, 7) A hybrid approach might use object wrappers for primitive IDs or maintain both a WeakMap and a traditional Map, 8) This change exemplifies the principle of designing systems that are resilient to memory management oversights.
Use arrays instead of Maps for better performance
Add a method to completely clear all resources
Store only primitive values as resources

Next Question (14/40)