c# (wcf) architecture file and directory structure (and instantiation) -

Hello and thanks for any help.

I have a wcf service that I'm trying to do properly modularize.

I know that there's interest in a better way or implementing the directory structure of files and instanciatation, there is a more appropriate way of abstraction that I might be missing?

Is this the best way? Especially if the ability to handle and display thousands of parallel requests

Present I have this following structure:?

-Root \ Service.cs

 Public Service Service: IService {Public Zero CreateCustomer (Customer Customer) {CustomerService customerService = New Customer Service (); CustomerService.Create (customer); } 
   Public Zero UpdateCustomer (Customer Customer) {CustomerService customerService = New Customer Service (); CustomerService.Update (customer); }  

}

-Root \ client \ CustomerService.cs

 pulbic class customerservice {public void (Make client) {// DO Public Zero update (customer client) {// do something} Delete Public Zero (Intel Customer ID) {// Something Things} Recover Public Customers (Intel Customer ID) {/ Do Something}  

}

Note:. I do not include customer object or DataAccess libraries in this example as I am only concerned about the service.

If you can tell me what you think, if you know better or a resource that can help you

Thank you kindly Steven

I web Services Used a software factory and liked its structure.

The structure was something like this in their sample code:

  BYA.Mfg.SCM.Svc.WCF source business logic BYA.Mfg.SCM.Svc.WCF.BusinessEntities BYA.Mfg.SCM.Svc WCF.BusinessLogic resource access BYA.Mfg.SCM.Svc.WCF.DataAccess service interface BYA.Mfg.SCM.Svc.WCF.DataContracts BYA.Mfg.SCM.Svc.WCF.FaultContracts BYA.Mfg.SCM.Svc.WCF. MessageContracts BYA.Mfg.SCM.Svc.WCF.ServiceContracts BYA.Mfg.SCM.Svc.WCF.ServiceImplementation Test