Remove DDD boilerplate

[adityamandaleeka]

From @bricelam:

It is the professional opinion of the EF team that the DDD patterns employed in the Ordering.API and related projects are of no value (and possibly even result in negative value) and can safely be removed for the sake of maintainability.

This includes, but is not limited to:

• [ ] Removing the types under the src/Ordering.Domain/SeedWork/ directory
• [ ] Use actual CLR enums for CardType and OrderStatus
• [ ] Update OrderQueries to use EF LINQ queries
  • Make ViewModel classes more idiomatic
• [ ] Consider Using IdentityGuid as the primary key (instead of the current surrogate key) for Buyer
• [ ] Review the unusual use of transactions and the SaveChanges call in TransactionBehavior

[adityamandaleeka]

@ajcvickers @bricelam Is there a timeline for when this will get done? Just wondering if it's for 11/14 or not.

[ajcvickers]

@adityamandaleeka No, this is a longer-term thing. We have to decide what to replace it with.

[davidfowl]

@ajcvickers Can we make some incremental progress (based on the above items) in the mean time? Some of those work items seem small.

[adityamandaleeka]

@SamMonoRT is this on your team's radar? Any idea when this will be worked on?

[SamMonoRT]

No wasn't on my radar, but now is. I'll review and update here, but at the moment this is below our cut line for 9.0 and we may not get to it anytime soon, given other priorities.