submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Standalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. Concurrent execution: multiple Spark applications work together Quick response: long-running Spark applications without startup cost Optimal execution plan: fully supports Spark compatible systems or plugins, you only need to take care of them as using them with regular Spark applications. For example, you can run Spark SQL engines created by the Kyuubi on any cluster manager, including

submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Standalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. Concurrent execution: multiple Spark applications work together Quick response: long-running Spark applications without startup cost Optimal execution plan: fully supports Spark compatible systems or plugins, you only need to take care of them as using them with regular Spark applications. For example, you can run Spark SQL engines created by the Kyuubi on any cluster manager, including

submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Stan- dalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. • Concurrent execution: multiple Spark applications work together • Quick response: long-running Spark applications without startup cost • Optimal execution plan: fully supports compatible systems or plugins, you only need to take care of them as using them with regular Spark applications. For example, you can run Spark SQL engines created by the Kyuubi on any cluster manager, including

submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Stan- dalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. • Concurrent execution: multiple Spark applications work together • Quick response: long-running Spark applications without startup cost • Optimal execution plan: fully supports compatible systems or plugins, you only need to take care of them as using them with regular Spark applications. For example, you can run Spark SQL engines created by the Kyuubi on any cluster manager, including

submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Stan- dalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. • Concurrent execution: multiple Spark applications work together • Quick response: long-running Spark applications without startup cost • Optimal execution plan: fully supports systems or plugins, you only need to take care of them as using them with regular Spark/Flink/Trino applications. For example, you can run Spark/Flink/Trino SQL engines created by the Kyuubi on any cluster manager

submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Stan- dalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. • Concurrent execution: multiple Spark applications work together • Quick response: long-running Spark applications without startup cost • Optimal execution plan: fully supports systems or plugins, you only need to take care of them as using them with regular Spark/Flink/Trino applications. For example, you can run Spark/Flink/Trino SQL engines created by the Kyuubi on any cluster manager

submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Standalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. Concurrent execution: multiple Spark applications work together Quick response: long-running Spark applications without startup cost Optimal execution plan: fully supports Spark compatible systems or plugins, you only need to take care of them as using them with regular Spark applications. For example, you can run Spark SQL engines created by the Kyuubi on any cluster manager, including

submit Spark applications to all supported cluster managers, including YARN, Mesos, Kubernetes, Standalone, and local. The SPA policy also make it possible for you to launch different applications against unified analytics engine. Concurrent execution: multiple Spark applications work together Quick response: long-running Spark applications without startup cost Optimal execution plan: fully supports Spark compatible systems or plugins, you only need to take care of them as using them with regular Spark applications. For example, you can run Spark SQL engines created by the Kyuubi on any cluster manager, including

metadata requests and receive metadata results. – It enables easy submission of self-contained applications for batch processing, such as Spark jobs. • MySQL Protocol – A MySQL-compatible interface that computing resources. Besides, Kyuubi also supports submissions of code snippets and self-contained applications serverlessly for more ad- vanced usage. 2.1 Ease of Use End users could have an optimized experience execution environments. Here we use Spark for demonstration. These essential components are JVM-based applications. So, the JRE needs to be pre-installed and the JAVA_HOME is correctly set to each component.

metadata requests and receive metadata results. – It enables easy submission of self-contained applications for batch processing, such as Spark jobs. • MySQL Protocol – A MySQL-compatible interface that computing resources. Besides, Kyuubi also supports submissions of code snippets and self-contained applications serverlessly for more ad- vanced usage. 2.1 Ease of Use End users could have an optimized experience execution environments. Here we use Spark for demonstration. These essential components are JVM-based applications. So, the JRE needs to be pre-installed and the JAVA_HOME is correctly set to each component.