How to better organize the web service interface

Question

I have a web service that has about 200 methods implemented using .Net + WCF in a standalone service. we model support code to use different handlers for different methods, but in the end there is another monolithic interface ... I used (and loved) RESTful interfaces in the past, especially for how they split one interface into separate domains. can it be achieved using web services without sharing a web service? I would like to hear thoughts about this.

Answer 1

Why don't you define several WCF front-end interfaces that should be implemented by one web service class that you do not want to share. Then you must expose each interface as a separate service, and they will all be covered by the same class.