Architecture Structure: should each page(UI/angular) has its own service that combines multiple entities or...
up vote
0
down vote
favorite
I'm working on an application that manages students’ grades, attendance and behavior incidents. On the front end(Angular) , there is a component to create behavior incidents. This component needs the list of homerooms(classes or group of students). The list is being pulled from ClassService. After selecting a homeroom, the list of students in the given homeroom are requested from StudentService. The UI needs to know the attendance(from AttendanceService) of the day for each student as well as the number of positive and negative points of the students based on the behavior incidents.
Should I gather all the service into a separate service to pull all the classes, students, attendance, etc that is specific to this UI/page?
Or
Should I keep the service corresponding to each entity be responsible for providing this data?
I am not sure what would be the “best” approach for this situation. I like the idea of a Vertical Slice Architecture presented by Jimmy Bogard.
angular service architecture aspnetboilerplate ef-core-2.0
add a comment |
up vote
0
down vote
favorite
I'm working on an application that manages students’ grades, attendance and behavior incidents. On the front end(Angular) , there is a component to create behavior incidents. This component needs the list of homerooms(classes or group of students). The list is being pulled from ClassService. After selecting a homeroom, the list of students in the given homeroom are requested from StudentService. The UI needs to know the attendance(from AttendanceService) of the day for each student as well as the number of positive and negative points of the students based on the behavior incidents.
Should I gather all the service into a separate service to pull all the classes, students, attendance, etc that is specific to this UI/page?
Or
Should I keep the service corresponding to each entity be responsible for providing this data?
I am not sure what would be the “best” approach for this situation. I like the idea of a Vertical Slice Architecture presented by Jimmy Bogard.
angular service architecture aspnetboilerplate ef-core-2.0
It really depends. I do prefer domain-specific approach if you use REST API for server side. In that case, you will have class service, student service, attendance function, and etc.
– wannadream
Nov 22 at 4:57
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm working on an application that manages students’ grades, attendance and behavior incidents. On the front end(Angular) , there is a component to create behavior incidents. This component needs the list of homerooms(classes or group of students). The list is being pulled from ClassService. After selecting a homeroom, the list of students in the given homeroom are requested from StudentService. The UI needs to know the attendance(from AttendanceService) of the day for each student as well as the number of positive and negative points of the students based on the behavior incidents.
Should I gather all the service into a separate service to pull all the classes, students, attendance, etc that is specific to this UI/page?
Or
Should I keep the service corresponding to each entity be responsible for providing this data?
I am not sure what would be the “best” approach for this situation. I like the idea of a Vertical Slice Architecture presented by Jimmy Bogard.
angular service architecture aspnetboilerplate ef-core-2.0
I'm working on an application that manages students’ grades, attendance and behavior incidents. On the front end(Angular) , there is a component to create behavior incidents. This component needs the list of homerooms(classes or group of students). The list is being pulled from ClassService. After selecting a homeroom, the list of students in the given homeroom are requested from StudentService. The UI needs to know the attendance(from AttendanceService) of the day for each student as well as the number of positive and negative points of the students based on the behavior incidents.
Should I gather all the service into a separate service to pull all the classes, students, attendance, etc that is specific to this UI/page?
Or
Should I keep the service corresponding to each entity be responsible for providing this data?
I am not sure what would be the “best” approach for this situation. I like the idea of a Vertical Slice Architecture presented by Jimmy Bogard.
angular service architecture aspnetboilerplate ef-core-2.0
angular service architecture aspnetboilerplate ef-core-2.0
asked Nov 22 at 4:19
Omar Olivo
23128
23128
It really depends. I do prefer domain-specific approach if you use REST API for server side. In that case, you will have class service, student service, attendance function, and etc.
– wannadream
Nov 22 at 4:57
add a comment |
It really depends. I do prefer domain-specific approach if you use REST API for server side. In that case, you will have class service, student service, attendance function, and etc.
– wannadream
Nov 22 at 4:57
It really depends. I do prefer domain-specific approach if you use REST API for server side. In that case, you will have class service, student service, attendance function, and etc.
– wannadream
Nov 22 at 4:57
It really depends. I do prefer domain-specific approach if you use REST API for server side. In that case, you will have class service, student service, attendance function, and etc.
– wannadream
Nov 22 at 4:57
add a comment |
active
oldest
votes
active
oldest
votes
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.
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%2f53423846%2farchitecture-structure-should-each-pageui-angular-has-its-own-service-that-co%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
It really depends. I do prefer domain-specific approach if you use REST API for server side. In that case, you will have class service, student service, attendance function, and etc.
– wannadream
Nov 22 at 4:57