Hi Julius,

DSpace 7 is not yet released or available for production.  So, information
on load balancing between several DSpace 7 instances is not yet available
(and I doubt it has been fully figured out, although some may have early
ideas).

I expect such setups will be figured out in the coming months as we get
closer to a Beta release of DSpace 7.0.  In the meantime, we do have Docker
tooling that is starting to be built around DSpace 7 (again, just for
development though at this time).  If Docker is of interest to your
developers / devOps engineers, take a look at
https://dspace-labs.github.io/DSpace-Docker-Images/ and the corresponding
GitHub project at https://github.com/DSpace-Labs/DSpace-Docker-Images

In summary, I think this sort of production setup investigation will/should
be done on the DSpace 7 Beta release (in preparation for the final
release).  We're working hard to get to Beta as soon as possible, but the
reality is that we are still at least a few months off (and we're working
also on a more detailed work estimate for DSpace Steering so that we can
provide a more detailed estimate/timeline to both them and the community).

Tim

On Wed, Apr 24, 2019 at 1:44 AM Julius Gruber <julius.gru...@tuwien.ac.at>
wrote:

> This is a question for developers or devOps engineers concerning the
> production setup of DSpace7.
>
>
> We are planning to use DSpace7 as our University’s repository. I am
> wondering what solutions other organizations use (or plan to use) for load
> balancing between several DSpace7 instances. In this scenario two or more
> instances of DSpace have to access the same database, handle server and
> asset store. If someone has already thought about how a production setup of
> DSpace7 could look like please post some keywords or a short description of
> your production setup.
>
>
> Thanks in advance
>
> Julius
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-devel.
> For more options, visit https://groups.google.com/d/optout.
>


-- 

Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-devel+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to