Jhipster frontend microservice
I am using Jhipster and really like it.
Instead of generating my microservice frontend integrated inside the gateway, I would like to generate a separate frontend microservice.
Instead of having gateway -> µservice-backend, I would have gateway -> µservice-frontend -> µservice-backend
My use case :
- userA has a physical device devicev1. userA logs in on the gateway. He can see the application for the devicev1.
- userB has a physical device devicev2 (different features than v1). userB logs in on the gateway. He can see the application for the devicev2. (the backend is a different µservice for v1 and v2)
- userC is using a virtual device. He will see and use again another frontend + backend
Some researches :
I understand this is a hard to maintain feature because we would have to inject the "µservice-frontend" module inside the gateway. (And now there is Angular + React).
The question was asked in 2016 :
- https://groups.google.com/forum/#!msg/jhipster-dev/8VfS2ma_lX0/NySAdWJhEgAJ
- https://github.com/jhipster/generator-jhipster/issues/3667
I suppose I can still do it by generating a "client only" application and link it separately (rewrite the url), but I loose all the monitoring/registry/security jhipster stack.
Sooo, I won't do it and keep everything in my gateway.
I could also have multiple gateways, but I was more willing to have load-on-demand modules, in the same application.
- More than one gateway in jhipster
To keep it clean, I can create different angular modules for my load-on-demand part. I can use git mono-repo to separate each version in separated repository and compose before compiling. They are a lot of solutions, but I would like to use a more µservice way.
Any solution or architectural good practice?
Thank you
microservices jhipster
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
add a comment |
I am using Jhipster and really like it.
Instead of generating my microservice frontend integrated inside the gateway, I would like to generate a separate frontend microservice.
Instead of having gateway -> µservice-backend, I would have gateway -> µservice-frontend -> µservice-backend
My use case :
- userA has a physical device devicev1. userA logs in on the gateway. He can see the application for the devicev1.
- userB has a physical device devicev2 (different features than v1). userB logs in on the gateway. He can see the application for the devicev2. (the backend is a different µservice for v1 and v2)
- userC is using a virtual device. He will see and use again another frontend + backend
Some researches :
I understand this is a hard to maintain feature because we would have to inject the "µservice-frontend" module inside the gateway. (And now there is Angular + React).
The question was asked in 2016 :
- https://groups.google.com/forum/#!msg/jhipster-dev/8VfS2ma_lX0/NySAdWJhEgAJ
- https://github.com/jhipster/generator-jhipster/issues/3667
I suppose I can still do it by generating a "client only" application and link it separately (rewrite the url), but I loose all the monitoring/registry/security jhipster stack.
Sooo, I won't do it and keep everything in my gateway.
I could also have multiple gateways, but I was more willing to have load-on-demand modules, in the same application.
- More than one gateway in jhipster
To keep it clean, I can create different angular modules for my load-on-demand part. I can use git mono-repo to separate each version in separated repository and compose before compiling. They are a lot of solutions, but I would like to use a more µservice way.
Any solution or architectural good practice?
Thank you
microservices jhipster
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
This is an interesting use case. Perhaps the best option will be having multiple clients. Since all your api calls go through the gateway you will still get a good coverage from the gateway int terms of security and monitoring. I don't think there is much the gateway/registry do to the frontend apps themselves rather they monitor and sercure traffic into your services
– usaganbi
Dec 4 '18 at 6:00
@usagandi so you mean I would need to use multiple (jhipster) gateway. One for each device version and redirect my user based on his configuration?
– Vincent KERDRAON
Dec 5 '18 at 16:26
*usaganbi haha. No not multiple gateways but rather multiple react or angular standalone applications. Just as you would if you were building a mobile app. You should be able to have multiple frontend applications(web/mobile) and all they would do is communicate via the gateway to their respective services. Does that make sense?
– usaganbi
Dec 5 '18 at 18:54
add a comment |
I am using Jhipster and really like it.
Instead of generating my microservice frontend integrated inside the gateway, I would like to generate a separate frontend microservice.
Instead of having gateway -> µservice-backend, I would have gateway -> µservice-frontend -> µservice-backend
My use case :
- userA has a physical device devicev1. userA logs in on the gateway. He can see the application for the devicev1.
- userB has a physical device devicev2 (different features than v1). userB logs in on the gateway. He can see the application for the devicev2. (the backend is a different µservice for v1 and v2)
- userC is using a virtual device. He will see and use again another frontend + backend
Some researches :
I understand this is a hard to maintain feature because we would have to inject the "µservice-frontend" module inside the gateway. (And now there is Angular + React).
The question was asked in 2016 :
- https://groups.google.com/forum/#!msg/jhipster-dev/8VfS2ma_lX0/NySAdWJhEgAJ
- https://github.com/jhipster/generator-jhipster/issues/3667
I suppose I can still do it by generating a "client only" application and link it separately (rewrite the url), but I loose all the monitoring/registry/security jhipster stack.
Sooo, I won't do it and keep everything in my gateway.
I could also have multiple gateways, but I was more willing to have load-on-demand modules, in the same application.
- More than one gateway in jhipster
To keep it clean, I can create different angular modules for my load-on-demand part. I can use git mono-repo to separate each version in separated repository and compose before compiling. They are a lot of solutions, but I would like to use a more µservice way.
Any solution or architectural good practice?
Thank you
microservices jhipster
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
I am using Jhipster and really like it.
Instead of generating my microservice frontend integrated inside the gateway, I would like to generate a separate frontend microservice.
Instead of having gateway -> µservice-backend, I would have gateway -> µservice-frontend -> µservice-backend
My use case :
- userA has a physical device devicev1. userA logs in on the gateway. He can see the application for the devicev1.
- userB has a physical device devicev2 (different features than v1). userB logs in on the gateway. He can see the application for the devicev2. (the backend is a different µservice for v1 and v2)
- userC is using a virtual device. He will see and use again another frontend + backend
Some researches :
I understand this is a hard to maintain feature because we would have to inject the "µservice-frontend" module inside the gateway. (And now there is Angular + React).
The question was asked in 2016 :
- https://groups.google.com/forum/#!msg/jhipster-dev/8VfS2ma_lX0/NySAdWJhEgAJ
- https://github.com/jhipster/generator-jhipster/issues/3667
I suppose I can still do it by generating a "client only" application and link it separately (rewrite the url), but I loose all the monitoring/registry/security jhipster stack.
Sooo, I won't do it and keep everything in my gateway.
I could also have multiple gateways, but I was more willing to have load-on-demand modules, in the same application.
- More than one gateway in jhipster
To keep it clean, I can create different angular modules for my load-on-demand part. I can use git mono-repo to separate each version in separated repository and compose before compiling. They are a lot of solutions, but I would like to use a more µservice way.
Any solution or architectural good practice?
Thank you
microservices jhipster
microservices jhipster
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
asked Nov 28 '18 at 6:38
Vincent KERDRAONVincent KERDRAON
838
838
This is an interesting use case. Perhaps the best option will be having multiple clients. Since all your api calls go through the gateway you will still get a good coverage from the gateway int terms of security and monitoring. I don't think there is much the gateway/registry do to the frontend apps themselves rather they monitor and sercure traffic into your services
– usaganbi
Dec 4 '18 at 6:00
@usagandi so you mean I would need to use multiple (jhipster) gateway. One for each device version and redirect my user based on his configuration?
– Vincent KERDRAON
Dec 5 '18 at 16:26
*usaganbi haha. No not multiple gateways but rather multiple react or angular standalone applications. Just as you would if you were building a mobile app. You should be able to have multiple frontend applications(web/mobile) and all they would do is communicate via the gateway to their respective services. Does that make sense?
– usaganbi
Dec 5 '18 at 18:54
add a comment |
This is an interesting use case. Perhaps the best option will be having multiple clients. Since all your api calls go through the gateway you will still get a good coverage from the gateway int terms of security and monitoring. I don't think there is much the gateway/registry do to the frontend apps themselves rather they monitor and sercure traffic into your services
– usaganbi
Dec 4 '18 at 6:00
@usagandi so you mean I would need to use multiple (jhipster) gateway. One for each device version and redirect my user based on his configuration?
– Vincent KERDRAON
Dec 5 '18 at 16:26
*usaganbi haha. No not multiple gateways but rather multiple react or angular standalone applications. Just as you would if you were building a mobile app. You should be able to have multiple frontend applications(web/mobile) and all they would do is communicate via the gateway to their respective services. Does that make sense?
– usaganbi
Dec 5 '18 at 18:54
This is an interesting use case. Perhaps the best option will be having multiple clients. Since all your api calls go through the gateway you will still get a good coverage from the gateway int terms of security and monitoring. I don't think there is much the gateway/registry do to the frontend apps themselves rather they monitor and sercure traffic into your services
– usaganbi
Dec 4 '18 at 6:00
This is an interesting use case. Perhaps the best option will be having multiple clients. Since all your api calls go through the gateway you will still get a good coverage from the gateway int terms of security and monitoring. I don't think there is much the gateway/registry do to the frontend apps themselves rather they monitor and sercure traffic into your services
– usaganbi
Dec 4 '18 at 6:00
@usagandi so you mean I would need to use multiple (jhipster) gateway. One for each device version and redirect my user based on his configuration?
– Vincent KERDRAON
Dec 5 '18 at 16:26
@usagandi so you mean I would need to use multiple (jhipster) gateway. One for each device version and redirect my user based on his configuration?
– Vincent KERDRAON
Dec 5 '18 at 16:26
*usaganbi haha. No not multiple gateways but rather multiple react or angular standalone applications. Just as you would if you were building a mobile app. You should be able to have multiple frontend applications(web/mobile) and all they would do is communicate via the gateway to their respective services. Does that make sense?
– usaganbi
Dec 5 '18 at 18:54
*usaganbi haha. No not multiple gateways but rather multiple react or angular standalone applications. Just as you would if you were building a mobile app. You should be able to have multiple frontend applications(web/mobile) and all they would do is communicate via the gateway to their respective services. Does that make sense?
– usaganbi
Dec 5 '18 at 18:54
add a comment |
0
active
oldest
votes
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%2f53513531%2fjhipster-frontend-microservice%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53513531%2fjhipster-frontend-microservice%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
This is an interesting use case. Perhaps the best option will be having multiple clients. Since all your api calls go through the gateway you will still get a good coverage from the gateway int terms of security and monitoring. I don't think there is much the gateway/registry do to the frontend apps themselves rather they monitor and sercure traffic into your services
– usaganbi
Dec 4 '18 at 6:00
@usagandi so you mean I would need to use multiple (jhipster) gateway. One for each device version and redirect my user based on his configuration?
– Vincent KERDRAON
Dec 5 '18 at 16:26
*usaganbi haha. No not multiple gateways but rather multiple react or angular standalone applications. Just as you would if you were building a mobile app. You should be able to have multiple frontend applications(web/mobile) and all they would do is communicate via the gateway to their respective services. Does that make sense?
– usaganbi
Dec 5 '18 at 18:54