This is a great question with a vision to decide future of a product. Let me fill in my thoughts. As a user: I was looking for a very good alternative for Kafka based upon its disadvantages. I am a techie looking for a better product looked into many products available in OpenSource world - ended up with Pulsar based upon its architecture and cloud adoption flexibility. Future lies on how it adopts to changing strategies in software world - Cloud. It is easy for me to launch Pulsar in Bare Metal in Cloud or on a Kubernetes Cluster or on a GKE or AKS etc. Features that are inflight will make Pulsar more robust. I believe Pulsar will make it BIG based on its Architecture and easy to launch. Regarding SO, I would say the visit is declining phase as many projects are available on IM. Considering my example, I am working on Jpos, Pulsar, reactor-core and Spring. They are available on Slack and Gitter respectively. I felt it is easy to connect like FTF with the leads and community. We can ping directly/work directly in case to solve a issue then and there. I felt this model is more productive. You can join the channel anytime and can search to find whether those questions are answered before like SO. My 2 cents.
[ Full content available at: https://github.com/apache/incubator-pulsar/issues/2462 ] This message was relayed via gitbox.apache.org for [email protected]
