hop VS Apache ZooKeeper

If you're looking for a visual and more intuitive way to load data to Neo4j, you might want to have a look at Apache Hop. Hop comes with tons of functionality to load data to Neo4j.

Apache Hop is a great open source orchestration platform with excellent native Neo4j support.

Have you checked out Apache Hop? https://hop.apache.org/ It is a very powerful no-code open source ETL tool.

Apache Hop https://hop.apache.org/

You could look into Apache Hop. Open source with Salesforce connectors. Powerful free option for reverse ETL. https://hop.apache.org/

I would get familiar with an ETL tool. Apache Hop is excellent, opensource, and has native support for neo4j. It will make your imports easier to see the "flow" - also easier to share/collaborate with others. It also gives you support to use several methods (direct from RDBMS, from CSV, or running code like your python example) all from within the same workflows/pipelines, so you can use the best method/tool for a particular part of your process.

I used Apache HOP as an ETL to integrate the ERP data from RangerMSP into a Neo4j knowledgegraph. Then connected the ERP data to our other vendors data using their web APIs (Office365/sharepoint/teams), backups, infrastructure monitoring/alerting to create other workflows that performed automations and validations of our service delivery. The reporting is so so much easier, faster, and more contextual since relationships are created as the data is built/modified, rather then when queried as in an RDBMS.

I'm a pentaho pdi user that wants to give a try to Apache Hop. I've started the gui and learned a bit how to import from pdi, create a new workflow/pipeline, made some test. Now I've to move on but reading the docs at https://hop.apache.org/ I can't find informations I need:

You can try Apache Hop

Apache ZooKeeper — a distributed coordination, synchronization, and configuration service (written in Java);

To use Kafka, we also need to deploy a service that keeps configuration informations such as Zookeeper.

Failure Detection and Recovery It’s not enough to have backup systems. It’s also crucial to detect failures quickly. Modern systems employ monitoring tools and rely on distributed coordination systems such as Zookeeper or etcd to identify faults in real-time: once detected, recovery mechanisms are triggered to restore the service.

zookeeper: is (was?) used for secrets management. it was also used as a basic health check, but has been since been replaced.

You can install Kafka from https://kafka.apache.org/quickstart. Because Druid and Kafka both use Apache Zookeeper, I opted to use the Zookeeper deployment that comes with Druid, so didn’t start it with Kafka. Once running, I created two topics for me to post the data into, and for Druid to ingest from:

Please note that we use Zookeeper as the Governance Center.

Next, review deployment complexity such as DB-less versus database-backed deployments. For example, Kong does require running Cassandra or Postgres. Apigee requires Cassandra, Zookeeper, and Postgres to run, while other solutions like Express Gateway and Tyk only require Redis. Apache APISIX uses etcd as its data store, it stores and manages routing-related and plugin-related configurations in etcd in the Data Plane.

ZooKeeper, a system for coordinating distributed nodes, similar to Google's Chubby

[Unit] Description=Apache Zookeeper server Documentation=http://zookeeper.apache.org Requires=network.target remote-fs.target After=network.target remote-fs.target [Service] Type=simple ExecStart=/usr/local/kafka/bin/zookeeper-server-start.sh /usr/local/kafka/config/zookeeper.properties ExecStop=/usr/local/kafka/bin/zookeeper-server-stop.sh Restart=on-abnormal [Install] WantedBy=multi-user.target

ElasticJob achieves distributed coordination through ZooKeeper. In practical scenarios, users may start multiple jobs in the same project simultaneously, all of which use the same Apache Curator client. There are certain risks due to the nature of ZooKeeper and the callback method of Curator in a single event thread.