#39;s underlying execution engine basically executes a series of stateful transformations</span>
<span class="sd">    on batches of data. The difficulty here is how much of that underlying API to expose here so it&#39;s still useful without the user having to understand </span>
<span class="sd">    how the Quokka runtime works. To that end, we have to come up with suitable partitioner and placement strategy abstraction classes and interfaces.</span>

<span class="sd">    If you are interested in helping us 