database

[MartijnR]

Code is written to facilitate asynchronous db actions (to replace the asynchronous filesystem actions).

Some considerations about picking a database solution that scales well:

• efficient data exports
• able to deal with large amount of simultaneous submissions (e.g. after server downtime)

[MartijnR]

dat is interesting!

[MartijnR]

It may be best to clearly define a connector API for a particular storage option/brand, and add one sample connector. Community to add additional ones.

So just choose a document storage service such as Digital Ocean Object storage or dat or Firebase, as the default without analysing if it's the really the best there is.

form.add(xml, resources)
form.update(xml, resources)
form.remove(formId)

record.add(xml, resources)
record.update(xml, resources)
record.remove(instanceId)

records.getAll(formId)
records.get(query)

define return values

(publishing should be separate from this, perhaps so that the same publishing options are available for all storage options)

[MartijnR]

BaseX is also interesting: http://basex.org/basex/server/

https://github.com/BaseXdb/basex