Adapter Pattern and packaging
up vote
0
down vote
favorite
I am working on a project that needs to be refactored in order to achieve decoupled modules.
I need to us an Adapter to decide which module to route to depending on some config.
+===========+
| Front-end |
+===========+
| |
+==================+ +==================+
| RESTful Service1 | | RESTful Service2 |
+==================+ +==================+
| |
+=========================+ +=========+
| Adapter | --- | Config |
+=========================+ +=========+
| | |
+=========+ +=========+ +=========+
| Module1 | | Module2 | | Module3 |
+=========+ +=========+ +=========+
I have a Java application, and want to package the modules in JARS using Maven.
RESTful Service1 will either talk to Module1 or Module2 while RESTful Service2 will always talk to Module3. I need to establish which is the nest way to package these modules.
RESTful Service1 will be in it's own Jar while Module1 and Module2 will have their own Jars too.
Question
Seeing that RESTful Service2 will always talk toModule3 only, should they be in the same Jar? Or should I separate them into two seperate Jars too?
Thanks
java design-patterns architecture
asked Nov 12 at 6:33
Richard
2,075432103
|
show 1 more comment
up vote
0
down vote
favorite
I am working on a project that needs to be refactored in order to achieve decoupled modules.
I need to us an Adapter to decide which module to route to depending on some config.
+===========+
| Front-end |
+===========+
| |
+==================+ +==================+
| RESTful Service1 | | RESTful Service2 |
+==================+ +==================+
| |
+=========================+ +=========+
| Adapter | --- | Config |
+=========================+ +=========+
| | |
+=========+ +=========+ +=========+
| Module1 | | Module2 | | Module3 |
+=========+ +=========+ +=========+
I have a Java application, and want to package the modules in JARS using Maven.
RESTful Service1 will either talk to Module1 or Module2 while RESTful Service2 will always talk to Module3. I need to establish which is the nest way to package these modules.
RESTful Service1 will be in it's own Jar while Module1 and Module2 will have their own Jars too.
Question
Seeing that RESTful Service2 will always talk toModule3 only, should they be in the same Jar? Or should I separate them into two seperate Jars too?
Thanks
java design-patterns architecture
asked Nov 12 at 6:33
Richard
2,075432103
Would you want to update RS2 when Module1 changes?
– Scary Wombat
Nov 12 at 6:38
@ScaryWombat the Modules just provide data in the response to the RESTful services. The RESTful services are stateless and just provide an interface for the front-end to get data from the modules. In the future, the modules and RESTful services may change, but they will always be inline with each other, i.e. if Module 1 or 2 changes, then RESTful Service1 will change. If Module3 changes, then only RESTful Service2 will change.
– Richard
Nov 12 at 6:42
Why is it that sometimes when I ask a question, people often do not answer the question but just give me more information that I may not want. (this time I left the question mark off the end)
– Scary Wombat
Nov 12 at 6:44
@ScaryWombat, I have updated my answer above. The answer is 'No'. RS2 and Module1 are not related. RS2 and Module3 are though.
– Richard
Nov 12 at 6:45
1
It is not good practice to put yourModule 3in with your REST web service. Web services should just handle the data transferring from your database. If you putModule 3into the RESTful web service then hopefully you needModule 3everywhere in future projects.
– Dom
Nov 12 at 16:59
|
show 1 more comment
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am working on a project that needs to be refactored in order to achieve decoupled modules.
I need to us an Adapter to decide which module to route to depending on some config.
+===========+
| Front-end |
+===========+
| |
+==================+ +==================+
| RESTful Service1 | | RESTful Service2 |
+==================+ +==================+
| |
+=========================+ +=========+
| Adapter | --- | Config |
+=========================+ +=========+
| | |
+=========+ +=========+ +=========+
| Module1 | | Module2 | | Module3 |
+=========+ +=========+ +=========+
I have a Java application, and want to package the modules in JARS using Maven.
RESTful Service1 will either talk to Module1 or Module2 while RESTful Service2 will always talk to Module3. I need to establish which is the nest way to package these modules.
RESTful Service1 will be in it's own Jar while Module1 and Module2 will have their own Jars too.
Question
Seeing that RESTful Service2 will always talk toModule3 only, should they be in the same Jar? Or should I separate them into two seperate Jars too?
Thanks
java design-patterns architecture
asked Nov 12 at 6:33
Richard
2,075432103
I am working on a project that needs to be refactored in order to achieve decoupled modules.
I need to us an Adapter to decide which module to route to depending on some config.
+===========+
| Front-end |
+===========+
| |
+==================+ +==================+
| RESTful Service1 | | RESTful Service2 |
+==================+ +==================+
| |
+=========================+ +=========+
| Adapter | --- | Config |
+=========================+ +=========+
| | |
+=========+ +=========+ +=========+
| Module1 | | Module2 | | Module3 |
+=========+ +=========+ +=========+
I have a Java application, and want to package the modules in JARS using Maven.
RESTful Service1 will either talk to Module1 or Module2 while RESTful Service2 will always talk to Module3. I need to establish which is the nest way to package these modules.
RESTful Service1 will be in it's own Jar while Module1 and Module2 will have their own Jars too.
Question
Seeing that RESTful Service2 will always talk toModule3 only, should they be in the same Jar? Or should I separate them into two seperate Jars too?
Thanks
java design-patterns architecture
java design-patterns architecture
asked Nov 12 at 6:33
Richard
2,075432103
asked Nov 12 at 6:33
Richard
2,075432103
asked Nov 12 at 6:33
Richard
2,075432103
asked Nov 12 at 6:33
Richard
2,075432103
asked Nov 12 at 6:33
Richard
2,075432103
2,075432103
Would you want to update RS2 when Module1 changes?
– Scary Wombat
Nov 12 at 6:38
@ScaryWombat the Modules just provide data in the response to the RESTful services. The RESTful services are stateless and just provide an interface for the front-end to get data from the modules. In the future, the modules and RESTful services may change, but they will always be inline with each other, i.e. if Module 1 or 2 changes, then RESTful Service1 will change. If Module3 changes, then only RESTful Service2 will change.
– Richard
Nov 12 at 6:42
Why is it that sometimes when I ask a question, people often do not answer the question but just give me more information that I may not want. (this time I left the question mark off the end)
– Scary Wombat
Nov 12 at 6:44
@ScaryWombat, I have updated my answer above. The answer is 'No'. RS2 and Module1 are not related. RS2 and Module3 are though.
– Richard
Nov 12 at 6:45
1
It is not good practice to put yourModule 3in with your REST web service. Web services should just handle the data transferring from your database. If you putModule 3into the RESTful web service then hopefully you needModule 3everywhere in future projects.
– Dom
Nov 12 at 16:59
|
show 1 more comment
Would you want to update RS2 when Module1 changes?
– Scary Wombat
Nov 12 at 6:38
@ScaryWombat the Modules just provide data in the response to the RESTful services. The RESTful services are stateless and just provide an interface for the front-end to get data from the modules. In the future, the modules and RESTful services may change, but they will always be inline with each other, i.e. if Module 1 or 2 changes, then RESTful Service1 will change. If Module3 changes, then only RESTful Service2 will change.
– Richard
Nov 12 at 6:42
Why is it that sometimes when I ask a question, people often do not answer the question but just give me more information that I may not want. (this time I left the question mark off the end)
– Scary Wombat
Nov 12 at 6:44
@ScaryWombat, I have updated my answer above. The answer is 'No'. RS2 and Module1 are not related. RS2 and Module3 are though.
– Richard
Nov 12 at 6:45
1
It is not good practice to put yourModule 3in with your REST web service. Web services should just handle the data transferring from your database. If you putModule 3into the RESTful web service then hopefully you needModule 3everywhere in future projects.
– Dom
Nov 12 at 16:59
Would you want to update RS2 when Module1 changes?
– Scary Wombat
Nov 12 at 6:38
Would you want to update RS2 when Module1 changes?
– Scary Wombat
Nov 12 at 6:38
@ScaryWombat the Modules just provide data in the response to the RESTful services. The RESTful services are stateless and just provide an interface for the front-end to get data from the modules. In the future, the modules and RESTful services may change, but they will always be inline with each other, i.e. if Module 1 or 2 changes, then RESTful Service1 will change. If Module3 changes, then only RESTful Service2 will change.
– Richard
Nov 12 at 6:42
@ScaryWombat the Modules just provide data in the response to the RESTful services. The RESTful services are stateless and just provide an interface for the front-end to get data from the modules. In the future, the modules and RESTful services may change, but they will always be inline with each other, i.e. if Module 1 or 2 changes, then RESTful Service1 will change. If Module3 changes, then only RESTful Service2 will change.
– Richard
Nov 12 at 6:42
Why is it that sometimes when I ask a question, people often do not answer the question but just give me more information that I may not want. (this time I left the question mark off the end)
– Scary Wombat
Nov 12 at 6:44
Why is it that sometimes when I ask a question, people often do not answer the question but just give me more information that I may not want. (this time I left the question mark off the end)
– Scary Wombat
Nov 12 at 6:44
@ScaryWombat, I have updated my answer above. The answer is 'No'. RS2 and Module1 are not related. RS2 and Module3 are though.
– Richard
Nov 12 at 6:45
@ScaryWombat, I have updated my answer above. The answer is 'No'. RS2 and Module1 are not related. RS2 and Module3 are though.
– Richard
Nov 12 at 6:45
1
1
It is not good practice to put your
Module 3 in with your REST web service. Web services should just handle the data transferring from your database. If you put Module 3 into the RESTful web service then hopefully you need Module 3 everywhere in future projects.– Dom
Nov 12 at 16:59
It is not good practice to put your
Module 3 in with your REST web service. Web services should just handle the data transferring from your database. If you put Module 3 into the RESTful web service then hopefully you need Module 3 everywhere in future projects.– Dom
Nov 12 at 16:59
|
show 1 more comment
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
Because RS2 when deployed always needs to work with M3, putting them in the same jar offers one benefit: we won’t forget M3 when deploying RS2. But the downside is that it is difficult to reuse and deploy M3 to another system which does not require RS2.
I think the benefit above is little. Often, when deploying a system you should have a document or checklist. Even if some component was forgotten, chance is that you could detect and fix it quickly.
So the better option is to seperate RS2 and M3 into two jars.
answered Nov 12 at 16:40
Nghia Bui
1,443812
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',
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%2f53256971%2fadapter-pattern-and-packaging%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
up vote
1
down vote
accepted
Because RS2 when deployed always needs to work with M3, putting them in the same jar offers one benefit: we won’t forget M3 when deploying RS2. But the downside is that it is difficult to reuse and deploy M3 to another system which does not require RS2.
I think the benefit above is little. Often, when deploying a system you should have a document or checklist. Even if some component was forgotten, chance is that you could detect and fix it quickly.
So the better option is to seperate RS2 and M3 into two jars.
answered Nov 12 at 16:40
Nghia Bui
1,443812
add a comment |
up vote
1
down vote
accepted
Because RS2 when deployed always needs to work with M3, putting them in the same jar offers one benefit: we won’t forget M3 when deploying RS2. But the downside is that it is difficult to reuse and deploy M3 to another system which does not require RS2.
I think the benefit above is little. Often, when deploying a system you should have a document or checklist. Even if some component was forgotten, chance is that you could detect and fix it quickly.
So the better option is to seperate RS2 and M3 into two jars.
answered Nov 12 at 16:40
Nghia Bui
1,443812
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
Because RS2 when deployed always needs to work with M3, putting them in the same jar offers one benefit: we won’t forget M3 when deploying RS2. But the downside is that it is difficult to reuse and deploy M3 to another system which does not require RS2.
I think the benefit above is little. Often, when deploying a system you should have a document or checklist. Even if some component was forgotten, chance is that you could detect and fix it quickly.
So the better option is to seperate RS2 and M3 into two jars.
answered Nov 12 at 16:40
Nghia Bui
1,443812
Because RS2 when deployed always needs to work with M3, putting them in the same jar offers one benefit: we won’t forget M3 when deploying RS2. But the downside is that it is difficult to reuse and deploy M3 to another system which does not require RS2.
I think the benefit above is little. Often, when deploying a system you should have a document or checklist. Even if some component was forgotten, chance is that you could detect and fix it quickly.
So the better option is to seperate RS2 and M3 into two jars.
answered Nov 12 at 16:40
Nghia Bui
1,443812
answered Nov 12 at 16:40
Nghia Bui
1,443812
answered Nov 12 at 16:40
Nghia Bui
1,443812
answered Nov 12 at 16:40
Nghia Bui
1,443812
1,443812
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f53256971%2fadapter-pattern-and-packaging%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
Would you want to update RS2 when Module1 changes?
– Scary Wombat
Nov 12 at 6:38
@ScaryWombat the Modules just provide data in the response to the RESTful services. The RESTful services are stateless and just provide an interface for the front-end to get data from the modules. In the future, the modules and RESTful services may change, but they will always be inline with each other, i.e. if Module 1 or 2 changes, then RESTful Service1 will change. If Module3 changes, then only RESTful Service2 will change.
– Richard
Nov 12 at 6:42
Why is it that sometimes when I ask a question, people often do not answer the question but just give me more information that I may not want. (this time I left the question mark off the end)
– Scary Wombat
Nov 12 at 6:44
@ScaryWombat, I have updated my answer above. The answer is 'No'. RS2 and Module1 are not related. RS2 and Module3 are though.
– Richard
Nov 12 at 6:45
1
It is not good practice to put your
Module 3in with your REST web service. Web services should just handle the data transferring from your database. If you putModule 3into the RESTful web service then hopefully you needModule 3everywhere in future projects.– Dom
Nov 12 at 16:59