Fewture Cannot be Now

So I was at Microsoft’s PDC this year. I had to make an international
trip just for that so it was not as stressful when I have had to
combine PDC with other work. It was pretty cool and people watching for
PDC news already know the meat and potatoes was “Cloud computing”.
Azure was announced and I was not at all surprised by the difference of
style between Bill Gates and Ray Ozzie.  Shocking or
not, whole theme was around Azure, Live Services, Live Framework, Live
Mesh and everything else that is live. I was personally interested in
MS Sync Framework and one of the guys from the team presented a
session around that. I had also met the presenter before and seen most of his
presentation before so technically there was not much I got out of this
PDC other than bringing home the news of all things online. I was
pleasantly surprised that MS had a lot of homework before coming to PDC
- setting up data centers (I will write about their ‘containerized’
data center), setting up web sites for testing by super excited PDC
folks etc.
Anyway, just wanted to write a quick note.. it has been
2-3 weeks since I got back and felt that I should at least write a note
before detailed accounts. or not.

DomainDrivenDesign.pdf states that:

……, if you use a PI-based approach for persistent objects, there’s no requirement to do any of the following:

• Inherit from a certain base class (besides object)
• Only instantiate via a provided factory
• Use specially provided datatypes, such as for collections
• Implement a specific interface
• Provide specific constructors
• Provide mandatory specific fields
• Avoid certain constructs

Unfortunately, people have forgotten the benefits of O/R Mapping. Too many generators, auto-gen classes, auto-gen database schemas, ato-gen mappings…. kinda throws the core value/benfit of O/R Mapping out the window. Separate domain, as detached as they could be/need to be – brought together by mapping.