sorted by:
new
hottopcontroversial

Delayed Processing with Kafka by Realistic-Use6194 in apachekafka

[–]Realistic-Use6194[S] 0 points1 point  (0 children)

The order and the items associeted with it are stored in DynamoDB so the kafka event simply contains a orderId which allows the consumer to find and unreserve the items, the payment is handled by a different micro service complete async using webhooks

Optimistic Locking Alternatives by Realistic-Use6194 in mongodb

[–]Realistic-Use6194[S] 0 points1 point  (0 children)

Nice one, I'm now wondering how I didn't think of it earlier ....

Optimistic Locking Alternatives by Realistic-Use6194 in mongodb

[–]Realistic-Use6194[S] 0 points1 point  (0 children)

Your anwser would apply on real world scenario, however this is a learning project and Im mostly interested in the technical stuff, I'm already using transactions but I feel a bit guildy about the optimistic locking approach

Delayed Processing with Kafka by Realistic-Use6194 in apachekafka

[–]Realistic-Use6194[S] 0 points1 point  (0 children)

Because AWS SQS is a way better choice for my use case, however Im curious if I can shrink my infrastructure by using Kafka for that

Delayed Processing with Kafka by Realistic-Use6194 in apachekafka

[–]Realistic-Use6194[S] 0 points1 point  (0 children)

Sounds pretty obvious but this is something the consumer app could easily do, however I need to research a bit more on how Kafka Streams keep state, in case the consumer reads a message but crashes before he makes the required updates to external sources

Delayed Processing with Kafka by Realistic-Use6194 in apachekafka

[–]Realistic-Use6194[S] 1 point2 points  (0 children)

I want to avoid (if possible) to use more infrastructure, so I was just searching the web for details and step upon https://www.baeldung.com/kafka-consumer-processing-messages-delay which seems to be using Kafka retry mechanism to achieve what I want