You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@ace.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2016/01/22 11:16:39 UTC

[jira] [Updated] (ACE-328) Analyze our options for different designs of the deployment repository.

     [ https://issues.apache.org/jira/browse/ACE-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

J.W. Janssen updated ACE-328:
-----------------------------
    Labels: ace-next  (was: )

> Analyze our options for different designs of the deployment repository.
> -----------------------------------------------------------------------
>
>                 Key: ACE-328
>                 URL: https://issues.apache.org/jira/browse/ACE-328
>             Project: ACE
>          Issue Type: Improvement
>          Components: Architecture, Deployment
>            Reporter: Marcel Offermans
>              Labels: ace-next
>
> The current deployment repository stores all deployment versions of all targets known to a server. This leads to a fast growing repository that, at some point, becomes hard to manage. One path is to optimize the way we store data in it. Another path is to consider other designs that improve scalability of this component. That's what this issue is about. We should start collecting design ideas and review them.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)