# How to bring your awesome mojo code in an existing data pipeline

**URL:** <https://forum.modular.com/t/how-to-bring-your-awesome-mojo-code-in-an-existing-data-pipeline/3502>\
**Category:** Share\
**Created:** [September 17, 2026, 4:36am UTC](https://forum.modular.com/t/how-to-bring-your-awesome-mojo-code-in-an-existing-data-pipeline/3502 "2026-09-17T04:36:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mseritan](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.modular.com/mseritan/32/130_2.png) [@mseritan](https://forum.modular.com/u/mseritan)\
**Post date:** [September 17, 2026, 4:36am UTC](https://forum.modular.com/t/how-to-bring-your-awesome-mojo-code-in-an-existing-data-pipeline/3502/1 "2026-09-17T04:36:42Z")

</div>

Here is a possible approach to start bringing some mojo goodness to your existing data pipelines:

> **[Arrow Flight to integrate your Mojo code in your legacy pipelines — magmalake](https://mlake.dev/blog/arrow-flight-as-an-interop-seam/)**
>
> Flight allows you to distribute processing between servers.

Comments and criticism appreciated!