Its been a while for me since I have developed with asp.net, I have a requirement to create a web api which will aggregate and reformat a myriad of other web services we use internally. What is the best practice for structuring code in a case like this? Outside of the Data / Model layout I have used previously, I intend to have models which describe the XML and JSON I am consuming as well as models which describe the JSON results I am returning to consumers. Does it make sense to create a namespace structure such as Domain.WebService{A..n} for each of the discrete webservices I will write business logic that produces results? It is expected that the data types being accessed will expand significantly from the initial XML and JSON it will consume initially and include database services etc?
↧