Home/ Questions/Q 8681693
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T21:34:37+00:00

I’m rearchitecting a large web forms ASP.Net application, inserting a service layer to take

  • 0

I’m rearchitecting a large web forms ASP.Net application, inserting a service layer to take away unwanted responsibility from the presentation layer.

I’ve seen a lot of examples where all the service methods are contained in one class.

Is this common / best practice? Or is it perfectly feasible to have a number of service classes within the service layer? I’m leaning towards having more than one service and those services being able to talk to each other.

Any guidance, pros/cons?

Richard

P.s. Note that I’m not talking about a web service layer, WCF or otherwsie, although that might become more relevant at a later date.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The SOLID principles, specifically the Single Responsibility Principle would suggest that having all of your functionality in one object is a bad idea, and i tend to agree. As your application grows the single class will become difficult to maintain.

    Your comments to Yuriys answer would suggest you want to use an IOC container. Lets consider that in more detail for a moment…

    The more functionality this single class contains, the more dependencies it will require. You could well end up having a constructor on the service that has a long list of parameters, simply because the class covers a lot of ground and depends on other functionality at a lower level, such as logging, database communication, authentication etc. Lets say a consumer of that service wants to call one, and only one specific method on that class before destroying the instance. Your IOC container will need to inject every dependency that the service could ‘possibly’ need at runtime, even though the consumer will only use maybe 1 or 2 of those dependencies.

    Also from an operational perspective – if you have more than one developer on the team working on the service layer at the same time, there is more possibility of merge conflicts if you are both editing one file. But, as suggested you could use partials to counter that issue.

    Usually a dose of practicality alongside a well known pattern or principle is the best way forward.

    I would suggest researching Service Orientated Architecture if you havent already, as it may help you answer some key decisions in the approach to your solution.

    • 0