JHipster Gateway with legacy REST service
I've setup a POC with the following components:
- JHipster registry
- JHipster API gateway
- 2 JHipster microservices
The communication works very well between these components.
Another requirement of my POC is to register an legacy webservice(SOAP or REST not developed with JHipster) in the JHipster gateway.
Is it possible?
I would want to use the API Gateway as a unique entry point for all the clients(external and internal)to access all the webservices of my company.
Thank you.
jhipster
add a comment |
I've setup a POC with the following components:
- JHipster registry
- JHipster API gateway
- 2 JHipster microservices
The communication works very well between these components.
Another requirement of my POC is to register an legacy webservice(SOAP or REST not developed with JHipster) in the JHipster gateway.
Is it possible?
I would want to use the API Gateway as a unique entry point for all the clients(external and internal)to access all the webservices of my company.
Thank you.
jhipster
The services are and will be developed with various technologies : SAP-Rest Odata, Spring boot(without JHipster), Soap or Rest services exposed by software providers (packages not managed by our company).
– user4325449
Nov 23 '18 at 8:26
How do you want to use these apps is not clear, do you want to expose through gateway or to call them for JHipster microservices ? Do you expect to benefit from rate limiting, circuit-breaking, load-balancing for legacy too? Could you describe the interactions between legacy apps and services ? Are these legacy services going to be called for client code on the gateway? Please edit your question rather than commenting
– Gaël Marziou
Nov 24 '18 at 10:17
add a comment |
I've setup a POC with the following components:
- JHipster registry
- JHipster API gateway
- 2 JHipster microservices
The communication works very well between these components.
Another requirement of my POC is to register an legacy webservice(SOAP or REST not developed with JHipster) in the JHipster gateway.
Is it possible?
I would want to use the API Gateway as a unique entry point for all the clients(external and internal)to access all the webservices of my company.
Thank you.
jhipster
I've setup a POC with the following components:
- JHipster registry
- JHipster API gateway
- 2 JHipster microservices
The communication works very well between these components.
Another requirement of my POC is to register an legacy webservice(SOAP or REST not developed with JHipster) in the JHipster gateway.
Is it possible?
I would want to use the API Gateway as a unique entry point for all the clients(external and internal)to access all the webservices of my company.
Thank you.
jhipster
jhipster
edited Nov 23 '18 at 16:59
user4325449
asked Nov 22 '18 at 20:21
user4325449user4325449
406
406
The services are and will be developed with various technologies : SAP-Rest Odata, Spring boot(without JHipster), Soap or Rest services exposed by software providers (packages not managed by our company).
– user4325449
Nov 23 '18 at 8:26
How do you want to use these apps is not clear, do you want to expose through gateway or to call them for JHipster microservices ? Do you expect to benefit from rate limiting, circuit-breaking, load-balancing for legacy too? Could you describe the interactions between legacy apps and services ? Are these legacy services going to be called for client code on the gateway? Please edit your question rather than commenting
– Gaël Marziou
Nov 24 '18 at 10:17
add a comment |
The services are and will be developed with various technologies : SAP-Rest Odata, Spring boot(without JHipster), Soap or Rest services exposed by software providers (packages not managed by our company).
– user4325449
Nov 23 '18 at 8:26
How do you want to use these apps is not clear, do you want to expose through gateway or to call them for JHipster microservices ? Do you expect to benefit from rate limiting, circuit-breaking, load-balancing for legacy too? Could you describe the interactions between legacy apps and services ? Are these legacy services going to be called for client code on the gateway? Please edit your question rather than commenting
– Gaël Marziou
Nov 24 '18 at 10:17
The services are and will be developed with various technologies : SAP-Rest Odata, Spring boot(without JHipster), Soap or Rest services exposed by software providers (packages not managed by our company).
– user4325449
Nov 23 '18 at 8:26
The services are and will be developed with various technologies : SAP-Rest Odata, Spring boot(without JHipster), Soap or Rest services exposed by software providers (packages not managed by our company).
– user4325449
Nov 23 '18 at 8:26
How do you want to use these apps is not clear, do you want to expose through gateway or to call them for JHipster microservices ? Do you expect to benefit from rate limiting, circuit-breaking, load-balancing for legacy too? Could you describe the interactions between legacy apps and services ? Are these legacy services going to be called for client code on the gateway? Please edit your question rather than commenting
– Gaël Marziou
Nov 24 '18 at 10:17
How do you want to use these apps is not clear, do you want to expose through gateway or to call them for JHipster microservices ? Do you expect to benefit from rate limiting, circuit-breaking, load-balancing for legacy too? Could you describe the interactions between legacy apps and services ? Are these legacy services going to be called for client code on the gateway? Please edit your question rather than commenting
– Gaël Marziou
Nov 24 '18 at 10:17
add a comment |
1 Answer
1
active
oldest
votes
Two important criteria are service discovery and security.
For service discovery, JHipster offers 2 options: JHipster Registry (Eureka) and HashiCorp Consul. Consul is better suited for legacy apps as it is less invasive because you can use DNS resolution and templates and a sidecar proxy approach.
For security, legacy apps should be able to consume authentication tokens to apply authorizations.
Is HashiCorp Consul equivalent to a product like WSO2 API Management?
– user4325449
Nov 23 '18 at 16:56
Not at all, please read their doc and JHipster's too jhipster.tech/consul
– Gaël Marziou
Nov 23 '18 at 18:34
Sorry for the mistake, I have the feeling that the couple JHipster gateway/Consul is equivalent to WSO2 API Management.
– user4325449
Nov 27 '18 at 16:03
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437606%2fjhipster-gateway-with-legacy-rest-service%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Two important criteria are service discovery and security.
For service discovery, JHipster offers 2 options: JHipster Registry (Eureka) and HashiCorp Consul. Consul is better suited for legacy apps as it is less invasive because you can use DNS resolution and templates and a sidecar proxy approach.
For security, legacy apps should be able to consume authentication tokens to apply authorizations.
Is HashiCorp Consul equivalent to a product like WSO2 API Management?
– user4325449
Nov 23 '18 at 16:56
Not at all, please read their doc and JHipster's too jhipster.tech/consul
– Gaël Marziou
Nov 23 '18 at 18:34
Sorry for the mistake, I have the feeling that the couple JHipster gateway/Consul is equivalent to WSO2 API Management.
– user4325449
Nov 27 '18 at 16:03
add a comment |
Two important criteria are service discovery and security.
For service discovery, JHipster offers 2 options: JHipster Registry (Eureka) and HashiCorp Consul. Consul is better suited for legacy apps as it is less invasive because you can use DNS resolution and templates and a sidecar proxy approach.
For security, legacy apps should be able to consume authentication tokens to apply authorizations.
Is HashiCorp Consul equivalent to a product like WSO2 API Management?
– user4325449
Nov 23 '18 at 16:56
Not at all, please read their doc and JHipster's too jhipster.tech/consul
– Gaël Marziou
Nov 23 '18 at 18:34
Sorry for the mistake, I have the feeling that the couple JHipster gateway/Consul is equivalent to WSO2 API Management.
– user4325449
Nov 27 '18 at 16:03
add a comment |
Two important criteria are service discovery and security.
For service discovery, JHipster offers 2 options: JHipster Registry (Eureka) and HashiCorp Consul. Consul is better suited for legacy apps as it is less invasive because you can use DNS resolution and templates and a sidecar proxy approach.
For security, legacy apps should be able to consume authentication tokens to apply authorizations.
Two important criteria are service discovery and security.
For service discovery, JHipster offers 2 options: JHipster Registry (Eureka) and HashiCorp Consul. Consul is better suited for legacy apps as it is less invasive because you can use DNS resolution and templates and a sidecar proxy approach.
For security, legacy apps should be able to consume authentication tokens to apply authorizations.
edited Nov 23 '18 at 9:54
answered Nov 23 '18 at 8:44
Gaël MarziouGaël Marziou
10.1k22535
10.1k22535
Is HashiCorp Consul equivalent to a product like WSO2 API Management?
– user4325449
Nov 23 '18 at 16:56
Not at all, please read their doc and JHipster's too jhipster.tech/consul
– Gaël Marziou
Nov 23 '18 at 18:34
Sorry for the mistake, I have the feeling that the couple JHipster gateway/Consul is equivalent to WSO2 API Management.
– user4325449
Nov 27 '18 at 16:03
add a comment |
Is HashiCorp Consul equivalent to a product like WSO2 API Management?
– user4325449
Nov 23 '18 at 16:56
Not at all, please read their doc and JHipster's too jhipster.tech/consul
– Gaël Marziou
Nov 23 '18 at 18:34
Sorry for the mistake, I have the feeling that the couple JHipster gateway/Consul is equivalent to WSO2 API Management.
– user4325449
Nov 27 '18 at 16:03
Is HashiCorp Consul equivalent to a product like WSO2 API Management?
– user4325449
Nov 23 '18 at 16:56
Is HashiCorp Consul equivalent to a product like WSO2 API Management?
– user4325449
Nov 23 '18 at 16:56
Not at all, please read their doc and JHipster's too jhipster.tech/consul
– Gaël Marziou
Nov 23 '18 at 18:34
Not at all, please read their doc and JHipster's too jhipster.tech/consul
– Gaël Marziou
Nov 23 '18 at 18:34
Sorry for the mistake, I have the feeling that the couple JHipster gateway/Consul is equivalent to WSO2 API Management.
– user4325449
Nov 27 '18 at 16:03
Sorry for the mistake, I have the feeling that the couple JHipster gateway/Consul is equivalent to WSO2 API Management.
– user4325449
Nov 27 '18 at 16:03
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53437606%2fjhipster-gateway-with-legacy-rest-service%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
The services are and will be developed with various technologies : SAP-Rest Odata, Spring boot(without JHipster), Soap or Rest services exposed by software providers (packages not managed by our company).
– user4325449
Nov 23 '18 at 8:26
How do you want to use these apps is not clear, do you want to expose through gateway or to call them for JHipster microservices ? Do you expect to benefit from rate limiting, circuit-breaking, load-balancing for legacy too? Could you describe the interactions between legacy apps and services ? Are these legacy services going to be called for client code on the gateway? Please edit your question rather than commenting
– Gaël Marziou
Nov 24 '18 at 10:17