Hi Oliver! Thanks for reaching out! What are you building yourself? Tell me morreeee.
Managed is an opportunity for sure, but it's complex for a boostrapped solo dev like myself. Supporting Helm charts and reference docker-compose files would be a start I think.
For the Kafka deployment, it a lot of places where I worked, to get Kafka streams, it was never just Kafka. It's say MSK, Schema Registry, tying those together, config-as-code for the topics, and setting this up in the local dev environment. That was a major pain to advocate for the first time this the benefits of streaming would be obvious.
3. For Typestream, Kafka is abstracted away pretty much entirely so I'm actually not positioning this towards people who already have Kafka deployed heavily. It's for those who do dual writes in their code, writing cronjobs for syncing, and have other secondary datastores.
I'm very much testing out the positioning by talking to whoever I can! What are you thinking?
Zapier builds automation tools for small business. We have been remote first since the company start and we are hiring across pretty much all departments: https://zapier.com/jobs
I'm an Engineering Manager on the Data team and we are looking for a Data Engineer experienced in security. We support the Data Warehouse Engineers by building infrastructure and tooling to make their jobs easier and increasing the rate we make data driven decision in the company. If it sounds like you might be a good fit, please apply! https://zapier.com/jobs/5105760002/data-engineer-open-to-mos...
Managed is an opportunity for sure, but it's complex for a boostrapped solo dev like myself. Supporting Helm charts and reference docker-compose files would be a start I think.
For the Kafka deployment, it a lot of places where I worked, to get Kafka streams, it was never just Kafka. It's say MSK, Schema Registry, tying those together, config-as-code for the topics, and setting this up in the local dev environment. That was a major pain to advocate for the first time this the benefits of streaming would be obvious.
3. For Typestream, Kafka is abstracted away pretty much entirely so I'm actually not positioning this towards people who already have Kafka deployed heavily. It's for those who do dual writes in their code, writing cronjobs for syncing, and have other secondary datastores.
I'm very much testing out the positioning by talking to whoever I can! What are you thinking?