If the application logic does not allow changing Kafka producer settings, how to guarantee delivery?

If changing Kafka producer settings is not possible, message delivery guarantees can be ensured through the following approaches:

• Using acknowledgments on the producer side: even without changing settings, the producer can wait for acknowledgments from the broker (acks) to ensure that the message is recorded.

• Implementing retries: in case of sending errors, the producer or client code should retry sending messages.

• Using idempotency: if the producer supports idempotency, it will help avoid duplication during retries.

• Configuring consumers: on the consumer side, processing with acknowledgment and re-reading messages in case of failures can be ensured.

• Monitoring and alerts: tracking queue status and delivery errors will allow quick response to issues.

Thus, message delivery guarantees can be achieved through architectural solutions and processing at the application and consumer levels, even if producer settings cannot be changed.