You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Mihaly Dallos (Jira)" <ji...@apache.org> on 2023/07/28 13:57:00 UTC

[jira] [Updated] (FINERACT-1824) Kafka connector for events and spring batch

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

Mihaly Dallos updated FINERACT-1824:
------------------------------------
    Description: 
 h3. Background
Any deployment can use Kafka as standard for messaging. Events should support it to remain on same tech stack. (not adding ActiveMQ to the mix).
 * Kafka topic for external events: fineract_external_events
 * Kafka topic for Spring Batch: fineract_batch_partitions

*Out of scope:*
Kafka infra (Creation of Amazon MSK)

{panel:title=Acceptance criteria}
 # Kafka connection can be configured via environment variables
 # Fineract can connect to Kafka to publish batch job work partitions and external events
{panel}

  was:
 
h3. Background

Any deployment can use Kafka as standard for messaging. Events should support it to remain on same tech stack. (not adding ActiveMQ to the mix).
 * Kafka topic for external events: fineract_external_events

 * Kafka topic for Spring Batch: fineract_batch_partitions

*Out of scope:*

Kafka infra (Creation of Amazon MSK)
*Acceptance criteria*
 # Kafka connection can be configured via environment variables

 # Fineract can connect to Kafka to publish batch job work partitions and external events


> Kafka connector for events and spring batch
> -------------------------------------------
>
>                 Key: FINERACT-1824
>                 URL: https://issues.apache.org/jira/browse/FINERACT-1824
>             Project: Apache Fineract
>          Issue Type: Improvement
>            Reporter: Mihaly Dallos
>            Assignee: Mihaly Dallos
>            Priority: Major
>              Labels: PepperSoup
>
>  h3. Background
> Any deployment can use Kafka as standard for messaging. Events should support it to remain on same tech stack. (not adding ActiveMQ to the mix).
>  * Kafka topic for external events: fineract_external_events
>  * Kafka topic for Spring Batch: fineract_batch_partitions
> *Out of scope:*
> Kafka infra (Creation of Amazon MSK)
> {panel:title=Acceptance criteria}
>  # Kafka connection can be configured via environment variables
>  # Fineract can connect to Kafka to publish batch job work partitions and external events
> {panel}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)