What is the difference between StreamPark's DataStream extensions and the plain Flink DataStream API?

StreamPark Core doesn't replace the Flink DataStream API; it extends it with methods and context that remove repetitive setup, while leaving the underlying Flink semantics untouched.

Plain Flink DataStream code typically starts with manually building a StreamExecutionEnvironment, wiring up parameter parsing, and hand-configuring each connector's source/sink boilerplate. StreamPark's extensions provide a RuntimeContext that already carries a configured environment and parsed parameters, plus extension methods on DataStream that wrap StreamPark's out-of-the-box connectors, so pulling from Kafka or writing to a common sink is a shorter call rather than a block of setup code.

The result compiles down to the same Flink DataStream job graph either way — StreamPark isn't introducing a new execution model. What changes is how much boilerplate the developer writes to reach that graph, which is exactly the "convention over configuration" trade StreamPark Core is built around.