When to use service or component in spring? For example, is a module responsible for sending email or common business logic a "service" or a "component"? and what's the difference? Is a service able to call the other services? Is there any transaction problem? or a service should call the components only? Someone told me that a service should never call the other services and should only call the components instead, which means Controller->Service->Component->DAO, but I found many people share the concept of Controller->Service->DAO with no component. Is there any system design criteria about this topic in Spring?

In order to "configure" Spring so it can provide you with the instances of the classes you need, you are supposed to tell Spring what objects are involved and how they are built. To do this you can use an xml configuration file or through annotations In case you take the annotation approach (IMHO a much better and simpler one) you can use <code>@Component</code> to annotate the class. This is like telling Spring: "Hey! I want you to know that you may need an instance of this class. Maybe because I request it, maybe because something I requested needs it". So annotating a class with <code>@Component</code> just let Spring know that it exists There are other annotations that do the same: <ul> <li> <code>@Controller</code> (and <code>@RestController</code>)</li> <li><code>@Service</code></li> <li><code>@Repository</code></li> </ul> They all inform Spring that the class is involved in the DI context. But they also have semantic meaning: <ul> <li> <code>@Controller</code> = <code>@Component</code> belonging to Presentation Layer</li> <li> <code>@Service</code> = <code>@Component</code> belonging to Service/Use Case Layer</li> <li> <code>@Repository</code> = <code>@Component</code> belonging to Persistence Layer</li> </ul> You can find more info in this question <blockquote> Should a service be able to call the other services? </blockquote> I don't see any problem with that. If any of your services requires to do some actions that are already performed by other you surely want to avoid code duplication. As long as you respect the architecture layers dependency (never going up) you'll be fine. About this you can check this article about Clean Architecture

When to use service or component in spring? [duplicate]

Tags:

java

spring

system-design

When to use service or component in spring?

For example, is a module responsible for sending email or common business logic a "service" or a "component"? and what's the difference?

Is a service able to call the other services? Is there any transaction problem? or a service should call the components only?

Someone told me that a service should never call the other services and should only call the components instead, which means Controller->Service->Component->DAO, but I found many people share the concept of Controller->Service->DAO with no component.

Is there any system design criteria about this topic in Spring?

287

asked Sep 18 '17 05:09

ChiaChih wu

1 Answers

In order to "configure" Spring so it can provide you with the instances of the classes you need, you are supposed to tell Spring what objects are involved and how they are built. To do this you can use an xml configuration file or through annotations

In case you take the annotation approach (IMHO a much better and simpler one) you can use @Component to annotate the class. This is like telling Spring: "Hey! I want you to know that you may need an instance of this class. Maybe because I request it, maybe because something I requested needs it". So annotating a class with @Component just let Spring know that it exists

There are other annotations that do the same:

@Controller (and @RestController)
@Service
@Repository

They all inform Spring that the class is involved in the DI context. But they also have semantic meaning:

@Controller = @Component belonging to Presentation Layer
@Service = @Component belonging to Service/Use Case Layer
@Repository = @Component belonging to Persistence Layer

You can find more info in this question

Should a service be able to call the other services?

I don't see any problem with that. If any of your services requires to do some actions that are already performed by other you surely want to avoid code duplication. As long as you respect the architecture layers dependency (never going up) you'll be fine.

About this you can check this article about Clean Architecture

answered Sep 23 '22 16:09

Alberto S.

Related questions
                            
                                newInstance() with inner classes
                            
                                Accessing JPA Data with REST fails No suitable HttpMessageConverter found
                            
                                How to make maven build of child module with parent module?
                            
                                how to create comma separated string in single quotes from arraylist of string in JAVA
                            
                                Efficiency of Multithreaded Loops
                            
                                Java - sort only subsection of array
                            
                                freemarker + spring configuration and simplest example
                            
                                Why does Java prefer to call double constructor?
                            
                                Maven Project creation command stuck
                            
                                multi module component scanning not working in spring boot
                            
                                How to check if a string is made only of letters and numbers
                            
                                I am getting DataSource Not Supported when using DataSouceBuilder
                            
                                Is remove() faster than get() in HashMap?
                            
                                How to script Gradle in order to publish shadowjar into Artifactory
                            
                                problems after installing java 8
                            
                                Java 8 Map: filter value and throw exception if match found
                            
                                Retrieving child value -firebase-
                            
                                Java8 Transform list of object to list of one attribute of object
                            
                                Mockito ambiguous method call
                            
                                How can I determine whether I am in a transaction in Spring?

Donate For Us

If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!

Donate Us With