Neo4j and fault tolerance

sirko-io / engine

Benefit from new browsers' technologies to speed up your site

GNU General Public License v3.0

43 stars 3 forks source link

Neo4j and fault tolerance #18

Closed dnesteryuk closed 7 years ago

dnesteryuk commented 7 years ago

The engine's modules must be restarted when:

[x] Neo4j goes down
- [x] Neo4j isn't accessible right away (it is possible when the engine gets started through the docker compose)

In both cases, the engine should retry to connect to Neo4j.

dnesteryuk commented 7 years ago

The second point is a little bit hard to achieve because this feature must be supplied by the library, for example, it is done for the bolt sips.

dnesteryuk commented 7 years ago

After migrating to the bolt sips, the project doesn't crash if Neo4j isn't accessible. The particular HTTP request might cause an error, but once Neo4j is accessible again, the project will normally work. The end user shouldn't be worried about restarting the project when Neo4j goes down.