Is it a bad practice to have a very extensive method within my class of service?
Or would it be better to break them down into smaller methods in the same class and call them?
Is it a bad practice to have a very extensive method within my class of service?
Or would it be better to break them down into smaller methods in the same class and call them?
Very extensive methods, in any layer, are bad. It is best to divide into smaller, reusable methods, where each method is concerned with a specific part of the processing. Submethods do not have to be public (and it's better that they are not) if it does not make sense to be called by other classes.