Why does Debezium Server With SQL Server requires Kafka?

[Ravinder Singh]

Hi 

I wanted to use Debezium Server in order to move away from Kafka system. My reasons for doing so was to have minimal recourses/infrastructure to kick off a project.

The challenge I faced with Deb Server 1.9 (back traced to 1.6) is the I must set up database.history.kafka.topic and database.history.kafka.bootstrap.servers when using SQL Server. (Note I have not tested if these are still needed for other DB).

[Ravinder Singh]

Sorry, I posted the above without complete. I am still new to Google Conversation.

So with SQL Server I still need to specify Kafka Topic and Kafka Server. Hence I cannot be Kafka free.

Please could you suggest anything so that I can avoid Kafka. As per Deb Server Docs it appears it should not require Kafka, but it still does.

I am using Docker for all of this, and files are attached. I have provided docker-compose file and also application.properties. Please place the application.properties inside conf folder before docker compose up.

[Oren Elias]

You can use alternative implementations to store the history topic. One of them is a FileBased provider where it will use a local file:
```
debezium.source.database.history=io.debezium.relational.history.FileDatabaseHistory
debezium.source.database.history.file.filename=data/history.dat
```

You can also use the Redis history writer to write these into a Stream in Redis:
```
debezium.source.offset.storage=io.debezium.server.redis.RedisOffsetBackingStore
```

> --
> You received this message because you are subscribed to the Google Groups "debezium" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/debezium/5f5d5f47-8d50-44ba-a150-5ddd365ace64n%40googlegroups.com.

[Ravinder Singh]

Thank you.

It works. I opted for the File based history.

Now next challenge :D

Thanks a tonne.