Mixing
Should I use api gateway for web application with embedded UI?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have some applications which have UI embedded in Django or ROR app. These applications do not have api but a monolithic web application which have UI and backend in a single module.
All the example I have seen talk about using api gateway for http api. Does it add any value to put such Django or ROR app behind an api gateway?
I am using Kong as api gateway. Not sure if Kong even works with such app. The documentation in Kong only talks about configuring services which are pure api.
If I do not put these applications behind api gateway, then I end up creating a mixed approach where some applications are behind api gateway and some are not. I definitely want to avoid this situation. This makes the whole configuration complex.
Any suggestions will be helpful.
microservices api-gateway kong
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
add a comment |
I have some applications which have UI embedded in Django or ROR app. These applications do not have api but a monolithic web application which have UI and backend in a single module.
All the example I have seen talk about using api gateway for http api. Does it add any value to put such Django or ROR app behind an api gateway?
I am using Kong as api gateway. Not sure if Kong even works with such app. The documentation in Kong only talks about configuring services which are pure api.
If I do not put these applications behind api gateway, then I end up creating a mixed approach where some applications are behind api gateway and some are not. I definitely want to avoid this situation. This makes the whole configuration complex.
Any suggestions will be helpful.
microservices api-gateway kong
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
add a comment |
I have some applications which have UI embedded in Django or ROR app. These applications do not have api but a monolithic web application which have UI and backend in a single module.
All the example I have seen talk about using api gateway for http api. Does it add any value to put such Django or ROR app behind an api gateway?
I am using Kong as api gateway. Not sure if Kong even works with such app. The documentation in Kong only talks about configuring services which are pure api.
If I do not put these applications behind api gateway, then I end up creating a mixed approach where some applications are behind api gateway and some are not. I definitely want to avoid this situation. This makes the whole configuration complex.
Any suggestions will be helpful.
microservices api-gateway kong
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
I have some applications which have UI embedded in Django or ROR app. These applications do not have api but a monolithic web application which have UI and backend in a single module.
All the example I have seen talk about using api gateway for http api. Does it add any value to put such Django or ROR app behind an api gateway?
I am using Kong as api gateway. Not sure if Kong even works with such app. The documentation in Kong only talks about configuring services which are pure api.
If I do not put these applications behind api gateway, then I end up creating a mixed approach where some applications are behind api gateway and some are not. I definitely want to avoid this situation. This makes the whole configuration complex.
Any suggestions will be helpful.
microservices api-gateway kong
microservices api-gateway kong
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
asked Jan 3 at 11:09
saurabhsaurabh
1,90811533
1,90811533
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
There is nothing wrong with monolithic applications behind a gateway and seems to be a recommended way.
You would benefit from Kong, as it provides different plugins, like Traffic Control or IP Restriction. Also you would have your configurations in a single place. So there are no reasons not to use gateway.
I do not know how your applications are exposed now, but when you will put them behind kong (or proxy) one thing you probably have to look at is client’s request IP: https://discuss.konghq.com/t/how-to-forward-clients-request-ip/384
answered Mar 18 at 15:30
IgorIgor
2551311
add a comment |
Making UI isolated from backend technology and implementation allow us to move to different UI technology if needed.
Due to that developing the backend as service/api make sense. In future if you want to move from Django to Angular to Android app, if backend is developed in the services/apis form then with out making any change in the backend we can move to any technology.
Once APIs comes into picture it is good to put all of them behind API gateway and implement all the common functionality in the API gateway. Like Authentication, authorization, logging, metering, monitoring and others.
For that Kong plays a role of that layer and provide most of the required features out of the box.
answered Feb 12 at 15:26
ShaleenShaleen
554512
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%2f54021131%2fshould-i-use-api-gateway-for-web-application-with-embedded-ui%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is nothing wrong with monolithic applications behind a gateway and seems to be a recommended way.
You would benefit from Kong, as it provides different plugins, like Traffic Control or IP Restriction. Also you would have your configurations in a single place. So there are no reasons not to use gateway.
I do not know how your applications are exposed now, but when you will put them behind kong (or proxy) one thing you probably have to look at is client’s request IP: https://discuss.konghq.com/t/how-to-forward-clients-request-ip/384
answered Mar 18 at 15:30
IgorIgor
2551311
add a comment |
There is nothing wrong with monolithic applications behind a gateway and seems to be a recommended way.
You would benefit from Kong, as it provides different plugins, like Traffic Control or IP Restriction. Also you would have your configurations in a single place. So there are no reasons not to use gateway.
I do not know how your applications are exposed now, but when you will put them behind kong (or proxy) one thing you probably have to look at is client’s request IP: https://discuss.konghq.com/t/how-to-forward-clients-request-ip/384
answered Mar 18 at 15:30
IgorIgor
2551311
add a comment |
There is nothing wrong with monolithic applications behind a gateway and seems to be a recommended way.
You would benefit from Kong, as it provides different plugins, like Traffic Control or IP Restriction. Also you would have your configurations in a single place. So there are no reasons not to use gateway.
I do not know how your applications are exposed now, but when you will put them behind kong (or proxy) one thing you probably have to look at is client’s request IP: https://discuss.konghq.com/t/how-to-forward-clients-request-ip/384
answered Mar 18 at 15:30
IgorIgor
2551311
There is nothing wrong with monolithic applications behind a gateway and seems to be a recommended way.
You would benefit from Kong, as it provides different plugins, like Traffic Control or IP Restriction. Also you would have your configurations in a single place. So there are no reasons not to use gateway.
I do not know how your applications are exposed now, but when you will put them behind kong (or proxy) one thing you probably have to look at is client’s request IP: https://discuss.konghq.com/t/how-to-forward-clients-request-ip/384
answered Mar 18 at 15:30
IgorIgor
2551311
answered Mar 18 at 15:30
IgorIgor
2551311
answered Mar 18 at 15:30
IgorIgor
2551311
answered Mar 18 at 15:30
IgorIgor
2551311
2551311
add a comment |
add a comment |
Making UI isolated from backend technology and implementation allow us to move to different UI technology if needed.
Due to that developing the backend as service/api make sense. In future if you want to move from Django to Angular to Android app, if backend is developed in the services/apis form then with out making any change in the backend we can move to any technology.
Once APIs comes into picture it is good to put all of them behind API gateway and implement all the common functionality in the API gateway. Like Authentication, authorization, logging, metering, monitoring and others.
For that Kong plays a role of that layer and provide most of the required features out of the box.
answered Feb 12 at 15:26
ShaleenShaleen
554512
add a comment |
Making UI isolated from backend technology and implementation allow us to move to different UI technology if needed.
Due to that developing the backend as service/api make sense. In future if you want to move from Django to Angular to Android app, if backend is developed in the services/apis form then with out making any change in the backend we can move to any technology.
Once APIs comes into picture it is good to put all of them behind API gateway and implement all the common functionality in the API gateway. Like Authentication, authorization, logging, metering, monitoring and others.
For that Kong plays a role of that layer and provide most of the required features out of the box.
answered Feb 12 at 15:26
ShaleenShaleen
554512
add a comment |
Making UI isolated from backend technology and implementation allow us to move to different UI technology if needed.
Due to that developing the backend as service/api make sense. In future if you want to move from Django to Angular to Android app, if backend is developed in the services/apis form then with out making any change in the backend we can move to any technology.
Once APIs comes into picture it is good to put all of them behind API gateway and implement all the common functionality in the API gateway. Like Authentication, authorization, logging, metering, monitoring and others.
For that Kong plays a role of that layer and provide most of the required features out of the box.
answered Feb 12 at 15:26
ShaleenShaleen
554512
Making UI isolated from backend technology and implementation allow us to move to different UI technology if needed.
Due to that developing the backend as service/api make sense. In future if you want to move from Django to Angular to Android app, if backend is developed in the services/apis form then with out making any change in the backend we can move to any technology.
Once APIs comes into picture it is good to put all of them behind API gateway and implement all the common functionality in the API gateway. Like Authentication, authorization, logging, metering, monitoring and others.
For that Kong plays a role of that layer and provide most of the required features out of the box.
answered Feb 12 at 15:26
ShaleenShaleen
554512
answered Feb 12 at 15:26
ShaleenShaleen
554512
answered Feb 12 at 15:26
ShaleenShaleen
554512
answered Feb 12 at 15:26
ShaleenShaleen
554512
554512
add a comment |
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%2f54021131%2fshould-i-use-api-gateway-for-web-application-with-embedded-ui%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
