StreamNative is enabling organizations to build the next generation of messaging and event streaming applications. Leveraging Apache Pulsar and Bookkeeper, we optimize for scalability and resiliency while reducing the overhead management and complexity required by incumbent technologies.
This position is for developing the core technologies around Apache Pulsar - the cloud-native event streaming system. To learn more about the project, checkout its website: https://pulsar.apache.org
Potential Projects
- Develop core technologies around Apache Pulsar and Apache BookKeeper
- Build ecosystems around Apache Pulsar and Apache BookKeeper
- Build developer communities of Apache Pulsar and Apache BookKeeper and publish technical posts
- Develop commercial products on Apache Pulsar and Apache BookKeeper
Ideal Background
- Excellent problem-solving skills, good communication skills, and teamwork spirit;
- Familiar with at least one language of Java/Python/Go/C++, with good programming skills;
- Familiar with the principles and key technologies of distributed systems. Knowledge and practice in distributed message middleware systems (such as Kafka/RabbitMQ) is preferred;
- Experience with big data systems (Hadoop, HDFS, Hive, Spark, Flink, etc.) is preferred;
- Experience with Docker, Kubernetes, Ansible/Terraform, etc. is preferred.
That’s good news! I guess it would be very helpful to formally address this concern. Is there something that has been written / published to that effect?
Note that this is a different goal from the KIP referenced above, which is to entirely remove any dependency on an external configuration service. The idea of “pluggable consensus” is explicitly rejected in this KIP.
