Best practice of storing complex Rdata objects

Posit Professional products
,
1

At this moment we are storing our reproducible result of a statistical analysis (e.g. LMM) as an R object which contains input data, parameters, models and output.

  1. Current situation:
    We use the serializeJSON function from the JSONlite package to create a very verbose JSON file which can be converted back to an .Rdata object by the unserializeJSON function

  2. Alternative situation:
    Store the complex object as .Rdata file and create plumber api’s to extract the data for non R applications.

In situation 1, the stored file can directly be used by other, non R, applications. But is this situation sustainable, which solution would provide the best compatibility for - future R versions - more complex and - larger objects?
Is there anyone who could share some experience or ideas about the best practice?

2

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.