-
jitsu
Jitsu is an open-source Segment alternative. Fully-scriptable data ingestion engine for modern data teams. Set-up a real-time data pipeline in minutes, not days
That's a good question. We're aiming to replace Kafka in some cases. There're many ways how people use Kafka. But it could be roughly divided into two buckets
- Kafka as a company wide message bus: dozen's of (micro)services sending data there, and consumers listens to data. Each service doesn't know which other service will consume the data. For that case, we're not looking to replace Kafka — we're going to work along with it. We have a PR about supporting Kafka as destination [1] (Jitsu sends data to Kafka), and we will support Kafka as a source at some point (PRs are always welcome :))
- Kafka is used just as a transport between web-app and DB. In that case Jitsu is a perfect replacement
[1] https://github.com/jitsucom/jitsu/pull/537
P. S. The same applies to Kinesis too
-
CodeRabbit
CodeRabbit: AI Code Reviews for Developers. Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
-
Congrats on your launch, and looks really exciting! I'm curious how this compares to tools like Snowplow [1]? I guess Jitsu comes with more sources and destinations out of the box?
[1] https://github.com/snowplow/snowplow
-
I mean, that's a common difference between a SaaS and a self-hosted solution. For a SaaS service a block list can include *.somesaas.com vs a self-hosted service that has it's own domain per owner, meaning you'd have to add every single one to the list. You can always find a common pattern in the URL (e.g. the API), and block based on something else. There's also an issue[0] to block based on POST body.
[0] https://github.com/uBlockOrigin/uBlock-issues/issues/1357
