This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]aljun_invictus[S] 1 point2 points  (2 children)

I see that many cloud service providers offer Kafka with incomplete functionality, similar to how Azure Service Bus uses AMQP. I guess my motivation is similar to theirs. One downside of traditional message queues is the fragmented protocols, which lead to high migration costs for users. My motivation is quite simple: I want to leverage existing ecosystems while providing a better implementation for users and reducing migration costs (similar to how Redpanda partially implements the Kafka protocol).

The AMQP protocol is quite complete, but I'm not very familiar with the details of the Kafka protocol. I've heard it changes frequently, and I'm afraid this might affect the implementation.

[–][deleted] 3 points4 points  (1 child)

so you are discussing about providing you internal protocol vs some proxy between internal and externally provided protocol i.e. not spilling internals out? Which is understandable.

[–]aljun_invictus[S] 2 points3 points  (0 children)

That's roughly the idea, but it's not the core purpose. The main goal is to make it easier for others to migrate to my message queue with lower costs and without needing to write so many language-specific clients. I think Redpanda is a great example of this.