You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "jannie cass (JIRA)" <ji...@apache.org> on 2018/03/18 07:18:00 UTC
[jira] [Commented] (ACE-374) Analysis: Batch job support
[ https://issues.apache.org/jira/browse/ACE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403889#comment-16403889 ]
jannie cass commented on ACE-374:
---------------------------------
very interesting work
> 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
> Priority: Major
> Fix For: 2.0.1
>
>
> 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
(v7.6.3#76005)