Currently our documentation kind of split between mentalities of "we provide a grab bag of tools that you already know how to use" and "we provide this example to cover this one specific use case" (often trying to show off as much as possible of the platform).
We could do a much better job at helping users guide themselves to the right tools for their given use case. This is especially bad since we have multiple cases where multiple tools we provide have a decently wide overlap (Spark/NiFi/Airflow, Trino/Druid/HBase, HDFS/S3/Minio (which isn't part of our platform per se, but is part of many demos)).
Currently our documentation kind of split between mentalities of "we provide a grab bag of tools that you already know how to use" and "we provide this example to cover this one specific use case" (often trying to show off as much as possible of the platform).
We could do a much better job at helping users guide themselves to the right tools for their given use case. This is especially bad since we have multiple cases where multiple tools we provide have a decently wide overlap (Spark/NiFi/Airflow, Trino/Druid/HBase, HDFS/S3/Minio (which isn't part of our platform per se, but is part of many demos)).