SOA: Principles of Service Design

Utter nonsense. Use a single POCO class that is totally separate from WCF; Entity; ASP.NET MVC and you can use it wherever you like. I suggest you read the [tomes from Thomas Erl](https://www.amazon.com/SOA-Principles-Service-Thomas-Erl/dp/0132344823). If you want to go around calling things `PersonDto`; `PersonEntity`; `PersonMvcModel` and `PersonClass` and `MyDatabaseConnectionClass` with the incredible amount of maintenance that goes with it, go right ahead. For someone who doesn't even know where to put things, you're quite opinionated and arrogant