Skip to content

Conversation

vincent-pochet
Copy link
Collaborator

@vincent-pochet vincent-pochet commented Mar 4, 2025

Context

This PR is related to getlago/lago#474

Description

The main goal is to add a Kafka consumer responsible for handling events charged in advance. It replace the the "hacky" approach used in the current post-processor implementation that is pushing Sidekiq jobs from the go service.

The consumer relies on the Karafka gem, making it easy to add new consumer in the future.

For now the EventsChargedInAdvanceConsumer will only enqueue a Events::PayInAdvanceJob for every message received in the topic, making it easy to keep the simple setup without kafka/clickhouse

@vincent-pochet vincent-pochet marked this pull request as ready for review March 6, 2025 09:19
@vincent-pochet vincent-pochet force-pushed the feat-kafka-in-advance-consumer branch 4 times, most recently from cc2bc55 to aa2d06e Compare March 11, 2025 11:12
@vincent-pochet vincent-pochet force-pushed the feat-kafka-in-advance-consumer branch from aa2d06e to fee89ad Compare March 11, 2025 13:44
@vincent-pochet vincent-pochet merged commit ff8e739 into main Mar 11, 2025
6 checks passed
@vincent-pochet vincent-pochet deleted the feat-kafka-in-advance-consumer branch March 11, 2025 15:05
ivannovosad added a commit that referenced this pull request Mar 12, 2025
annvelents pushed a commit that referenced this pull request Mar 17, 2025
…3291)

## Context

This PR is related to getlago/lago#474

## Description

The main goal is to add a Kafka consumer responsible for handling events
charged in advance. It replace the the "hacky" approach used in the
current post-processor implementation that is pushing Sidekiq jobs from
the go service.

The consumer relies on the Karafka gem, making it easy to add new
consumer in the future.

For now the `EventsChargedInAdvanceConsumer` will only enqueue a
`Events::PayInAdvanceJob` for every message received in the topic,
making it easy to keep the simple setup without kafka/clickhouse
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants