-
There is regularly a need to replay events through our pipelines and, usually, only to a subset of consumers in a given pipeline.
In telecom, we've implemented this using a field in the envelope "r…
-
For context, I'm the maintainer of https://rubygems.org/gems/redis and https://rubygems.org/gems/redis-client, and I was chatting with @stockholmux a few days ago about what I think is a recurrent pai…
-
The existing client already incorporates support for retrials. Should an error occur during execution and it's not a `readTimeout`, the command undergoes retrying within the `_process` function. Howev…
-
## Describe the bug
I am aware of the fix in #896. However, even using SDK versions that include the fix (AWS Kotlin SDK 0.32.0-beta), we run into frequent, unhandled networking exceptions when talki…
-
Hello I am working on a project where we are trying to simulate an eshop flow using event driven approach, and in some services we would like to have EoS.
Our flow is one service(A) sends an event t…
-
[P1874](https://wg21.link/p1874) has an ABI impact as it applies to named modules.
Header-units are affected, but as they have no distinct object file, existing ABI features support the requirement…
-
Consumer `group.id` should not be set by default.
When you launch a scenario a first with a consumer group set via `group.id` Kafka will register the offset read by this consumer group.
If you laun…
-
I'll make a command that will be executed via a forthcoming task runner. The command needs to be idempotent. It's similar to the `deploy-admin-server.sh` script used to deploy the admin app; differenc…
-
Hello,
In trying to understand missionary, I have followed your recommendation to go over the task and flow specifications first.
I thought perhaps trying to formalize them or rephrase them might …
-
**Description:**
The Idempotent Customer design pattern is essential in microservices architectures to ensure that repeated processing of the same request does not produce different outcomes. This pat…