Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zuul with Eureka or Consul #408

Open
raoul2502 opened this issue Feb 27, 2018 · 5 comments
Open

Zuul with Eureka or Consul #408

raoul2502 opened this issue Feb 27, 2018 · 5 comments
Labels

Comments

@raoul2502
Copy link

Hi@ all,

we are planning to built our next projects using microservices-architecture and we have already defined that we want to use Zuul as API-Gateway. Right now we have to decide which service registry we will use:

Consul or Eureka.

We want to use server-side load balancing (via Zuul itself). Is it possible to do this while combining Zuul with Consul or Eureka?

Furthermore, we don’t want to use self-registration pattern! Our plan is to use Third-Party registration! Is it possible while combining Zuul with Consul or Eureka? Which tools can be used for this? Are there alternatives for Registrator which works for Docker?

Thanks a lot in advance for your help!

@artgon
Copy link
Contributor

artgon commented Mar 1, 2018

Zuul is generally designed to be used with Eureka, that would be the recommended approach.

@sandy-adi
Copy link

Do you guys publish your packages in some repository or you encourage building from source?
I understand there could be cases where I have to modify the source and it makes sense to build from source, but other wise if I'd like to use the packages as is what is the best repository to look at?

@spencergibb
Copy link

AFAIK Netflix have not released binaries in the 2.1 branch, only 1.x

@artgon
Copy link
Contributor

artgon commented Mar 6, 2018

You can find the snapshot builds here: https://oss.jfrog.org/artifactory/oss-snapshot-local/com/netflix/zuul/zuul-core/2.1.1-SNAPSHOT/

We'll do a full release once we document it properly and announce it on our blog.

Copy link

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants