[ https://issues.apache.org/jira/browse/ACE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797898#comment-13797898
]
Marcel Offermans commented on ACE-374:
--------------------------------------
The analysis and design will be documented here:
https://cwiki.apache.org/confluence/display/ACE/Analysis+and+design+for+batch+jobs
> Analysis: Batch job support
> ---------------------------
>
> Key: ACE-374
> URL: https://issues.apache.org/jira/browse/ACE-374
> Project: ACE
> Issue Type: Task
> Components: Client Repository
> Reporter: Marcel Offermans
> Assignee: Marcel Offermans
>
> When scaling up, ACE might end up with lots of "customers" or tenants that, for example,
share a single shop. In such cases, when you update the shop, you need to iterate over all
customers and update their target and deployment repositories.
> What we need is a generic batch job support process that allows us to queue such jobs
easily. This task is about writing an analysis on how best to implement this.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
|