hey @nabetse, great that you are working on the persistence integration. If possible share your implementation, etc. such that I or people in the community can have a look at your approach.
First, good catch on the argument handling for the RAM provider. Indeed, the RAM provider does not check for void, undefined inputs. I will update this.
However, the RAM provider is currently a proposal for a simple in-memory implementation of the persistence interface and is not merged to baseline repo yet.
I really like the idea of creating a shared PR for the integration of the RAM provider into BRI-1, since this would be the next best step.
Nevertheless, I suggest to wait until the PR including the RAM provider is eventually merged to baseline master in order to start with the integration because requirements for the provider my change or the implementation of the provider itself may change.
If you have fixes for the issues regarding the void, undefined inputs, let me know and I will merge them to the provider.
Second, I dont know if I understand your question regarding the ram usage during testing correctly. I assume your complain is about the docker image size of BRI-1 images, since the RAM provider itself does not depend on any image but indeed uses RAM to store the records. Maybe you can elaborate more on your issues.