Assuming OAI content can be managed (issue #192), an improved persistence mechanism would make the service more scalable (content) and easier to scale (horizontal scale behind a balancer).
An alternative persistence that would be better for all but trivial uses would be a very simple database... the minimum to implement OAI is one step beyond a simple key-value store: {identifier,datestamp,document}.
The current filesystem impl is a key value store of {identifier,document} so it has to scan all records for some OAI requests.
Assuming OAI content can be managed (issue #192), an improved persistence mechanism would make the service more scalable (content) and easier to scale (horizontal scale behind a balancer).
An alternative persistence that would be better for all but trivial uses would be a very simple database... the minimum to implement OAI is one step beyond a simple key-value store: {identifier,datestamp,document}.
The current filesystem impl is a key value store of {identifier,document} so it has to scan all records for some OAI requests.