Title (Goal) | Autoscaling Servers |
---|---|
Primary Actor | Infrastructure Architects, Engineers, and Moonlighters |
Scope | Filesystem |
Level | Low |
Author | Brad Spry |
Story (A paragraph or two describing what happens) | If As an infrastructure engineer, I want Fedora's storage to be shareable in read/write fashion to a multiplicity of servers. Specifically, Fedora's objectStore, resourceIndex, and datastreamStore could should all be asynchronous friendly, storage could be shared by a multiplicity of servers. Additional servers can could then be programmed to launch automatically based upon a load threshold, and in reverse, programmed to terminate themselves when there is no load. Scale up with massive ingests, and scale down when ingest is complete. Scale up when a public digital collection suddenly becomes very popular, and scale down when popularity subsides. |