GitHub user hansva added a comment to the discussion: Apache Airflow vs Hop Server (vs Hop-run)
The reasons we tell people not to use the Hop Server: - It is stateless (reboot and everything is gone) - It has no scheduling - It does not have an easy API to add workflows/pipelines to the server - It is lacking good user management and dashboarding The server was originally designed to be an extension of your local GUI. It was used to act as a remote location to test and run the things you were designing locally because you might not have access to a DB on your local machine, or not enough resources. After that, it was extended to add some fun features, such as using it as an endpoint to provide the results of an executed pipeline. Now for the actual scheduling problem... It all depends on your needs, requirements, and architecture. If you are building workflows that need to run on fixed intervals, and you know the resources required. A single instance and crontab with regular Hop run will be the simplest deployment. You don't know your workloads, they can be triggered externally, users need an overview of what happened, it needs to be scalable? Then you end up with an airflow deployment with scalable infrastructure. >From personal experience, except for the we need an endpoint to provide data >to another system use case. We never use Hop Server. Kr, Hans GitHub link: https://github.com/apache/hop/discussions/5654#discussioncomment-14252393 ---- This is an automatically sent email for users@hop.apache.org. To unsubscribe, please send an email to: users-unsubscr...@hop.apache.org
