Creating two services and connecting them
So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.
Service A has two task:
- Accept HTTP request that carry money information
- Generate AMQP messages towards "Service B"
Service B has two tasks:
- Service accepts AMQP messages generated by Service A
- Service must have account entity stored in database, described by two properties, balance and updatedAt
I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.
php laravel service
asked Nov 22 at 11:40
zlatangoralija
168
add a comment |
So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.
Service A has two task:
- Accept HTTP request that carry money information
- Generate AMQP messages towards "Service B"
Service B has two tasks:
- Service accepts AMQP messages generated by Service A
- Service must have account entity stored in database, described by two properties, balance and updatedAt
I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.
php laravel service
asked Nov 22 at 11:40
zlatangoralija
168
add a comment |
So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.
Service A has two task:
- Accept HTTP request that carry money information
- Generate AMQP messages towards "Service B"
Service B has two tasks:
- Service accepts AMQP messages generated by Service A
- Service must have account entity stored in database, described by two properties, balance and updatedAt
I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.
php laravel service
asked Nov 22 at 11:40
zlatangoralija
168
So I've been given a project where my ultimate goal will be to create two services, service A and service B, and use a messaging system to connect them to single business process.
Service A has two task:
- Accept HTTP request that carry money information
- Generate AMQP messages towards "Service B"
Service B has two tasks:
- Service accepts AMQP messages generated by Service A
- Service must have account entity stored in database, described by two properties, balance and updatedAt
I understand the basic concept of creating this project and doing these tasks for both services, but I don't understand how am I supposed to create these services. Should they be a separate project or I can create them in a single Laravel project? Is there a Laravel functionality for creating services? I've been reading a lot of stuff for a few days but I can't find a solution yet. If you can provide any info or instructions, I'll be thankful. If you need any more info about a project, let me know.
php laravel service
php laravel service
asked Nov 22 at 11:40
zlatangoralija
168
asked Nov 22 at 11:40
zlatangoralija
168
asked Nov 22 at 11:40
zlatangoralija
168
asked Nov 22 at 11:40
zlatangoralija
168
asked Nov 22 at 11:40
zlatangoralija
168
168
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.
Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,
- Change our way of thought tied to database and joining data across tables to show data
- Don't create separate services just for the sake of doing it.
- Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus
- Micro services should be independently scalable (horizontal scaling)
- Think of micro services as something which solves a specific business problem
answered Nov 22 at 14:44
Jeevan
1326
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%2f53430210%2fcreating-two-services-and-connecting-them%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
I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.
Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,
- Change our way of thought tied to database and joining data across tables to show data
- Don't create separate services just for the sake of doing it.
- Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus
- Micro services should be independently scalable (horizontal scaling)
- Think of micro services as something which solves a specific business problem
answered Nov 22 at 14:44
Jeevan
1326
add a comment |
I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.
Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,
- Change our way of thought tied to database and joining data across tables to show data
- Don't create separate services just for the sake of doing it.
- Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus
- Micro services should be independently scalable (horizontal scaling)
- Think of micro services as something which solves a specific business problem
answered Nov 22 at 14:44
Jeevan
1326
add a comment |
I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.
Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,
- Change our way of thought tied to database and joining data across tables to show data
- Don't create separate services just for the sake of doing it.
- Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus
- Micro services should be independently scalable (horizontal scaling)
- Think of micro services as something which solves a specific business problem
answered Nov 22 at 14:44
Jeevan
1326
I think you are thinking of using a micro service architecture, in which case it should be two different projects where the projects don't share any code or data and communicates only through messages or APIs.
Micro service architecture is something very difficult to get a hold of when we are always used to working on monolithic architecture. Few pointers,
- Change our way of thought tied to database and joining data across tables to show data
- Don't create separate services just for the sake of doing it.
- Each service should be independent and should communicate to other services by exposing APIs or pushing/pulling data from some message bus
- Micro services should be independently scalable (horizontal scaling)
- Think of micro services as something which solves a specific business problem
answered Nov 22 at 14:44
Jeevan
1326
answered Nov 22 at 14:44
Jeevan
1326
answered Nov 22 at 14:44
Jeevan
1326
answered Nov 22 at 14:44
Jeevan
1326
1326
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%2f53430210%2fcreating-two-services-and-connecting-them%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
