3 ms·

I take it you don't write a lot of CRUD apps? You deal with a lot of data that is of only a few simple types, and as I said in my post, interoperability means

by jokerx 8y ago

I take it you don't write a lot of CRUD apps? You deal with a lot of data that is of only a few simple types, and as I said in my post, interoperability means you can't get too crazy with your class definitions. They need to stay simple or the SYSTEM will become more complicated. As for a variable never staying a simple type, again, see my example in my previous post. A string id is going to stay a string id and its data and behavior is dictated by being an id to remain supersimple. I am not against defining new types; I am against defining a new type for every single variable "just because."

scarface74 8y ago
For interoperability, you would want to keep the models that are sent out over the wire separate from the models you use in your program. You want the freedom of being able to change your database properties and fields, your domain models which could be some type of crazy aggregation of separate database tables are even information from other sources, without changing the structure that you expose to external clients.