Open matsduf opened 1 year ago
The biggest complaint I have about this is that it makes Backend into a datastore for business data of other applications. IMHO that's just not sound architecture.
Should we, however, decide that we do want other applications to store their stuff inside Backend I have three other complaints, but those are technical in nature and I'm providing an alternative design proposal that remedies them.
Technical complaints:
Design proposal:
job_create
that accepts an arbitrary JSON value and defaults to null. If RPCAPI.enable_client_data is false, the arbitrary JSON values must be null.batch_create
accept an object that maps domain names to arbitrary JSON values. If RPCAPI.enable_client_data is false, all the arbitrary JSON values must be null.job_results
response include a client_data property if and only if RPCAPI.enable_client_data is true.
When we run a batch test on the entire .se zone (or a random selection of that) we need to add registrar information for the interpretation of the result. For best performance we need that in the test_results table, but there is currently not place for that. We would like to have an extra field, preferably in JSON format to be able to add whatever subfields that we might need.
No other API calls need to support the custom data. For the use case, direct database queries are used to access the test results.