
Apache Pulsar: configuring tiered-storage (aws s3) via helm
In the third part of our blog post series “getting started with pulsar on kubernetes” we setup tiered storage (aws s3) with pulsar’s helm chart.
In the third part of our blog post series “getting started with pulsar on kubernetes” we setup tiered storage (aws s3) with pulsar’s helm chart.
In the second part of our blog post series “getting started with pulsar on kubernetes” we create a very simple pulsar producer and consumer. It will use json Serde and the project setup includes dockerization of the application and a simple helm chart to deploy it on Kubernetes.
In the 4th part of our blog post series “processing GDELT data with SCDF on kubernetes” we will reimplement the deduplication filter from the last post as a kafka streams application including custom SerDes.
In the first part of our blog post series “getting started with pulsar on kubernetes” we go through the steps of deploying the core components of Apache Pulsar on Kubernetes.
We are going to publish a couple of blog post about Apache Pulsar and how to run it on Kubernetes.
In the third part of our blog post series “processing GDELT data with SCDF on kubernetes” we want to filter the stream created in the last post as it contains a lot of duplicate data.