Our site is very new to Kafka. We received advise not to make use of the Kafka Rest Proxy, but rather to use the Kafka Clients ie Java. WHich is fine, but we sit with lot of legacy systems, where it would be lot easier just to use the KAFKA Rest Proxy.
I’m curious if any of you had bad experiences with the Rest Proxy, and would advise us to stay away from it?
We’re a university, so the traffic is not going to be a match for traffic thru Netflix or other sites.
From a performance perspective, adding native TCP Kafka clients would indeed be better than HTTP based services.
You don’t need to use the REST Proxy, either. You could write your own purpose specific HTTP services that your legacy services would hit. Either way, you’ll need to add some new dependencies to those systems.
The above response from @OneCricketeer is spot-on. REST Proxy service is not mandatory in your case. If you cannot leverage Kafka client libraries and build applications using them, then you can either go with REST Proxy or build your own HTTP service (for example using Spring framework)
From experience, a REST Proxy might work for your university workloads, but would not be able to support a high throughput scenario. In such cases, multiple REST Proxies need to be deployed with a front-end load balancer to spread the load across all the REST Proxies.
Hope that helps!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.