Next steps

You’ve built a pipeline, orchestrated it from a workflow, handled a failure path, and put both in a project. That is the core loop of working with Hop. Everything else is more of it.

Where you go next depends on what you’re trying to do.

Build more pipelines

Orchestrate more

Connect to your data

  • Databases - relational connections and the drivers Hop ships

  • VFS - read and write on AWS, Azure and GCP as if they were local files

  • Change Data Capture - log sniffing, filtered selection and snapshot comparison

  • Metadata types - everything you can define once and reuse

Run it somewhere else

Work like a team

  • Working with git - commit, diff and browse history from inside Hop Gui

  • Best Practices - what experienced Hop developers wish they had known

  • Linting - static checks on pipelines, workflows and metadata, locally or in CI

Coming from Kettle or PDI?

Get help

Hop is an Apache project, and the community is where questions get answered. See the community pages for the mailing lists, chat and issue tracker.