Eureka VS restQL-core

I was setting up microservices based on Netflix Eureka and experimenting on top of spring-cloud and after weeks of research and development the question rose!

The closest thing I've found is Netflix's Eureka, though its very Java oriented and I found hard to use.

There's an open issue documenting this problem on Spring Cloud Netflix and Netflix Eureka.

if you want to get more knowledge of the services, eureka etc, you can debug it. but I will digest you use the library instead of the annotations: https://github.com/Netflix/eureka

Service discovery — Traditionally provided by platforms like Netflix Eureka or Consul.

With multiple services running, it’s hard to discover where they’re located. The dependencies between multiple services are not always easily found, and new services may be deployed with a new dependency on an older service. Those services can be deployed anywhere in the infrastructure, so what you need is a Service Discovery service. There are plenty available, such as Netflix Eureka or HashiCorp Consul.

/network/shortestPath?node1=<>&node2=<>

to get a list of all devices but I'm basically just writing custom Cipher code to do that query and the benefits of Neo4J basically go out the door. It still has some interesting Graph features but if all i'm doing is writing a custom endpoint for every use case it's mainly pointless.

You can do a simple POST statement which takes a Neo4J query and execute it with some caching on top of it for sure.

Either ways in order to make Neo4J worth it I need a way to make the queries more dynamic. So right now I'm thinking of:

- restQL http://restql.b2w.io/