Symfony event vs service
Hi I have a question about symfony application architecture,
In my application I create different user, but when a user is created, updated, deleted, or his picture change, I need to do some action.
What is the best way to do this ? I excluded to do this on a controller action. There is 2 others solutions :
Create differents events like user.created, user.updated, ... And dispatch it on the controller action and make different listener to do the different action like MailListener (for user.created) TaskListener (for user.created) for add a task.
Use a service like UserManager and on this service have a method like userCreated() and on this method call differents actions like sendMailOnCreated, addTaskOnCreated for example.
For you what is the best method ?
symfony events service
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
add a comment |
Hi I have a question about symfony application architecture,
In my application I create different user, but when a user is created, updated, deleted, or his picture change, I need to do some action.
What is the best way to do this ? I excluded to do this on a controller action. There is 2 others solutions :
Create differents events like user.created, user.updated, ... And dispatch it on the controller action and make different listener to do the different action like MailListener (for user.created) TaskListener (for user.created) for add a task.
Use a service like UserManager and on this service have a method like userCreated() and on this method call differents actions like sendMailOnCreated, addTaskOnCreated for example.
For you what is the best method ?
symfony events service
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
As usual the answer is: it depends. An event based system is very flexible. If you need to do something else on user.create then you can just plugin another listener. On the other hand, a user manager lets you bring all the functionality together in one place and might be easier to maintain. My inclination is to use events but there is no "best" method.
– Cerad
Nov 20 '18 at 13:14
add a comment |
Hi I have a question about symfony application architecture,
In my application I create different user, but when a user is created, updated, deleted, or his picture change, I need to do some action.
What is the best way to do this ? I excluded to do this on a controller action. There is 2 others solutions :
Create differents events like user.created, user.updated, ... And dispatch it on the controller action and make different listener to do the different action like MailListener (for user.created) TaskListener (for user.created) for add a task.
Use a service like UserManager and on this service have a method like userCreated() and on this method call differents actions like sendMailOnCreated, addTaskOnCreated for example.
For you what is the best method ?
symfony events service
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
Hi I have a question about symfony application architecture,
In my application I create different user, but when a user is created, updated, deleted, or his picture change, I need to do some action.
What is the best way to do this ? I excluded to do this on a controller action. There is 2 others solutions :
Create differents events like user.created, user.updated, ... And dispatch it on the controller action and make different listener to do the different action like MailListener (for user.created) TaskListener (for user.created) for add a task.
Use a service like UserManager and on this service have a method like userCreated() and on this method call differents actions like sendMailOnCreated, addTaskOnCreated for example.
For you what is the best method ?
symfony events service
symfony events service
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
asked Nov 20 '18 at 11:36
eldiablo62eldiablo62
65110
65110
As usual the answer is: it depends. An event based system is very flexible. If you need to do something else on user.create then you can just plugin another listener. On the other hand, a user manager lets you bring all the functionality together in one place and might be easier to maintain. My inclination is to use events but there is no "best" method.
– Cerad
Nov 20 '18 at 13:14
add a comment |
As usual the answer is: it depends. An event based system is very flexible. If you need to do something else on user.create then you can just plugin another listener. On the other hand, a user manager lets you bring all the functionality together in one place and might be easier to maintain. My inclination is to use events but there is no "best" method.
– Cerad
Nov 20 '18 at 13:14
As usual the answer is: it depends. An event based system is very flexible. If you need to do something else on user.create then you can just plugin another listener. On the other hand, a user manager lets you bring all the functionality together in one place and might be easier to maintain. My inclination is to use events but there is no "best" method.
– Cerad
Nov 20 '18 at 13:14
As usual the answer is: it depends. An event based system is very flexible. If you need to do something else on user.create then you can just plugin another listener. On the other hand, a user manager lets you bring all the functionality together in one place and might be easier to maintain. My inclination is to use events but there is no "best" method.
– Cerad
Nov 20 '18 at 13:14
add a comment |
1 Answer
1
active
oldest
votes
For me, your first solution is the best one. It's clearly a use case for the Event component. It will be easier to maintain and more readable.
Moreover, if you need to add more listener you just need to create another one and bind it to your event. You don't need to modify your controller anymore.
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
I don't understand why this should be easier to maintain or more readable. In the end you would replace the event emit with a method call, nothing else. Therefore unit testing events is more difficult I think than just using a normal service. If the above application is not a bundle, which shouldn't be used from 3rd party, then I would stick with the service solution.
– baris1892
Nov 20 '18 at 19:15
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%2f53392166%2fsymfony-event-vs-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
For me, your first solution is the best one. It's clearly a use case for the Event component. It will be easier to maintain and more readable.
Moreover, if you need to add more listener you just need to create another one and bind it to your event. You don't need to modify your controller anymore.
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
I don't understand why this should be easier to maintain or more readable. In the end you would replace the event emit with a method call, nothing else. Therefore unit testing events is more difficult I think than just using a normal service. If the above application is not a bundle, which shouldn't be used from 3rd party, then I would stick with the service solution.
– baris1892
Nov 20 '18 at 19:15
add a comment |
For me, your first solution is the best one. It's clearly a use case for the Event component. It will be easier to maintain and more readable.
Moreover, if you need to add more listener you just need to create another one and bind it to your event. You don't need to modify your controller anymore.
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
I don't understand why this should be easier to maintain or more readable. In the end you would replace the event emit with a method call, nothing else. Therefore unit testing events is more difficult I think than just using a normal service. If the above application is not a bundle, which shouldn't be used from 3rd party, then I would stick with the service solution.
– baris1892
Nov 20 '18 at 19:15
add a comment |
For me, your first solution is the best one. It's clearly a use case for the Event component. It will be easier to maintain and more readable.
Moreover, if you need to add more listener you just need to create another one and bind it to your event. You don't need to modify your controller anymore.
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
For me, your first solution is the best one. It's clearly a use case for the Event component. It will be easier to maintain and more readable.
Moreover, if you need to add more listener you just need to create another one and bind it to your event. You don't need to modify your controller anymore.
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
answered Nov 20 '18 at 13:18
JacobDelcroixJacobDelcroix
262
262
I don't understand why this should be easier to maintain or more readable. In the end you would replace the event emit with a method call, nothing else. Therefore unit testing events is more difficult I think than just using a normal service. If the above application is not a bundle, which shouldn't be used from 3rd party, then I would stick with the service solution.
– baris1892
Nov 20 '18 at 19:15
add a comment |
I don't understand why this should be easier to maintain or more readable. In the end you would replace the event emit with a method call, nothing else. Therefore unit testing events is more difficult I think than just using a normal service. If the above application is not a bundle, which shouldn't be used from 3rd party, then I would stick with the service solution.
– baris1892
Nov 20 '18 at 19:15
I don't understand why this should be easier to maintain or more readable. In the end you would replace the event emit with a method call, nothing else. Therefore unit testing events is more difficult I think than just using a normal service. If the above application is not a bundle, which shouldn't be used from 3rd party, then I would stick with the service solution.
– baris1892
Nov 20 '18 at 19:15
I don't understand why this should be easier to maintain or more readable. In the end you would replace the event emit with a method call, nothing else. Therefore unit testing events is more difficult I think than just using a normal service. If the above application is not a bundle, which shouldn't be used from 3rd party, then I would stick with the service solution.
– baris1892
Nov 20 '18 at 19:15
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%2f53392166%2fsymfony-event-vs-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
As usual the answer is: it depends. An event based system is very flexible. If you need to do something else on user.create then you can just plugin another listener. On the other hand, a user manager lets you bring all the functionality together in one place and might be easier to maintain. My inclination is to use events but there is no "best" method.
– Cerad
Nov 20 '18 at 13:14