You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by je...@apache.org on 2019/10/16 19:30:03 UTC

[pulsar.wiki] branch master updated: Created PIP 46: Next-gen Proxy (markdown)

This is an automated email from the ASF dual-hosted git repository.

jerrypeng pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/pulsar.wiki.git


The following commit(s) were added to refs/heads/master by this push:
     new df9980d  Created PIP 46: Next-gen Proxy (markdown)
df9980d is described below

commit df9980d2498c61c9b0567417cf8584ed7727b32f
Author: Boyang Jerry Peng <je...@gmail.com>
AuthorDate: Wed Oct 16 12:29:59 2019 -0700

    Created PIP 46: Next-gen Proxy (markdown)
---
 PIP-46:-Next-gen-Proxy.md | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/PIP-46:-Next-gen-Proxy.md b/PIP-46:-Next-gen-Proxy.md
new file mode 100644
index 0000000..bb3a64a
--- /dev/null
+++ b/PIP-46:-Next-gen-Proxy.md
@@ -0,0 +1,16 @@
+* **Status**: Proposal
+* **Author**: Jerry Peng
+* **Pull Request**:
+* **Mailing List discussion**:
+* **Release**:
+
+## Goals
+
+Currently the proxy is used simply to forward messages to brokers but it has the potential to be much more.  I propose to develop a next-gen version of the proxy that allows the proxy to become more pluggable and able to support more ways to publish and consume message from Pulsar. The next-gen proxy will not serve its uses as a traditional proxy but also become a translation layer for Pulsar that allows different protocols to be able to interact with a Pulsar cluster. This will help att [...]
+
+**Initial design goals:**
+
+* Support different methods to publish and consume such as via http
+* Support different wire protocol from other messaging/streaming systems.  For example, allowing users to use Apache Kafka producers and consumers to be able to produce and consume messages from an Apache Pulsar cluster. When can support a wide variety of wire protocols but I think we should prioritize the following ones:
+  1. Apache Kafka
+  2. MQTT