NEX Object/subject persistence

[MikeHawkesCapventis]

Proposed change

When restarting NEX, we have to re-register all the subjects and reload things already in the object store. Can the NEX service have an option to persist 'important' NEX services on a fresh start?

Use case

I'm concerned that a fresh start of NEX will require a lot of needless transfers and an additional maintenance headache. The objects already exist in NEXCLIFILES, so we're duplicating effort during a startup phase, and introducing a new maintenance task. Perhaps anything needing persistence could end up in the KV store - key=subject, value=object key. Rattle through these on start. Anything not needing persistence isn't added to the KV store, so will die on restart; kill the KV and NEXCLIFILES buckets to do a fresh start.

Contribution

No response