Documentation of Jitsu and Alternatives
Problem
We want to outline and estimate a potential Jitsu replacement in #384589 (closed). In order to do this we first need to decide which alternative is the most valid one to pursue further.
There is already knowledge distributed across different issues / epics around potential replacements and alternatives that were considered at the start but no place where all considered solutions can be looked up and compared easily.
Desired Outcome
All Jitsu alternatives we considered are collected here as a root level comment in the structure outlined below. Even solutions that have only been discussed briefly but been discarded due to valid reasons should be documented. Based on the pros and cons of the discussed alternatives we decide on a single one to further outline and estimate for #384589 (closed).
Comparison Details
The comparison needs to take into account the requirements outlined in &9346 (closed). As described there, any proposed solution does not need to cover all features covered by Jitsu. A combination of different solutions is possible. For any "write-our-own" solutions a very rough outline of a potential architecture (e.g. writing to an event-streaming platform like Kafka) would be helpful.
Outline for a comment describing a solution
Name of the Solution (with Link if appropriate)
Overview
...
Feature-Set
...(should include which steps from the epic the solution covers)
Deployment (SaaS / SM)
...
Connection to Clickhouse
...
Advantages
...
Disadvantages
...