We have some applications which want to communicate with Kafka using REST API calls to both consume and produce messages. If we do not want to use Confluent REST Proxy, what are the options ?
2
votes
Your question needs more context. REST Proxy is a good solution, so what's the reason not to use it? That will drive the answer. If it's technical, what technical issue? If it's something else, what is that reason?
- Robin Moffatt
Hi Robin, the reason is monetary.
- Anirban
REST Proxy is completely open source. There is no monetary attachment to it
- OneCricketeer
Hi @cricket_007, We are thinking of not buying any additional hardware for this new request and use existing configuration to meet the requirement.I am mostly interested to know if consumer/producer can be created to meet this requirement.
- Anirban
Hi @cricket_007, I will check kafka-rest-start. I was thinking if we can create Rest-API calls which will be used by other applications to consume data from Kafka and push data to Kafka
- Anirban
2 Answers
2
votes
One possible alternative is the Strimzi Kafka Bridge (https://github.com/strimzi/strimzi-kafka-bridge). It's part of the broader Strimzi project about running Kafka on Kubernetes but work even running as standalone (when your Kafka cluster is on bare metal). Of course it's open source and Apache 2.0 licensed.
1
votes
the reason [not to use it] is monetary
You can use the Confluent REST Proxy with no software/licensing costs.
We are thinking of not buying any additional hardware for this new request and use existing configuration to meet the requirement.I am mostly interested to know if consumer/producer can be created to meet this requirement
You don't need extra hardware.
Pick an existing server with at least 2GB available of memory, and run kafka-rest-start and see how well it works
if we can create Rest-API calls which will be used by other applications to consume data from Kafka and push data to Kafka
That's the main purpose of REST Proxy, yes.
