Skip to main content

CONDG Entity Framework Presentation Follow-ups

Thanks to everyone who came out last night (73...a great showing considering the start of Memorial Day weekend and the Indiana Jones IV opening) to CONDG for my Entity Framework presentation. We had some great questions I didn't know the answers to which I'll investigate and respond to soon.
  • Is there a caching mechanism for ObjectContext? Thinking of this in a web (ASP.NET), disconnected between request/response environment.
  • Is the conceptual, mapping, and schema XML loaded up all at once or is the XML representing entities loaded up individually upon instantiation / use?
  • The EF wizard interrogates the physical data store and produces the 1:1, Type per Table initial EDM. Is it possible to model the EDM first leveraging it to generate the physical schema?
  • Referring to this performance comparison between the traditional Sql Client, Entity SQL, and LINQ to Entities, what's the break-down of time consumed?
    • The ADO.NET team posted a follow-up with the break-down here. Granted, it's beta3 bits but there is some fascinating insight into the innards of EF on this post. Here is the final installment of posts on performance.
  • (I responded to this one but want to delve in further...) Are transactions built into EF and the ObjectContext? Is the ObjectContext transaction-aware?
  • Is the EF and ObjectContext interface based? Meaning, can I leverage a mock testing framework to unit test my EDM?
  • Clarification on lazy loading in EF. Thanks to Kevin Sprague for correcting me on how NHibernate handles both lazy and eager loading.
    • I can't state it any better than the EF FAQ. Lazy loading is the default but eager loading is supported on a query-by-query basis. One needs to explicitly call Load (or Include) to pull related entities into the object graph. Related postings on lazy loading here, here and here.

Comments

Popular posts from this blog

Hero Write-up: Now this is Customer Service!

My best friend Scott is president/C-everything of a small northeastern Ohio manufacturing concern, KirkKey Interlock . I hadn't spoken with him for a while and wanted to see how Canton fared with the Blizzard of '08 (that's what they're calling it...not me). I say, "So what's new?" He replies that on Tuesday his primary server (which essentially runs the business) came up with lame with not one, but [a statistically improbable] *two* physical disk failures on a RAID5 hardware array. My friend attempts the fix but gives up pretty quickly after seeing some Linux nasty-grams on the boot screen. His service provider is an old college buddy who lives down in Raleigh, Cerient Technologies led by Jason Tower . Scott couldn't email out because Exchange was on the toasted server. Being creative, Scott started Treo-emailing photos of the screen. Unfortunately, Jason couldn't receive email because a storm had knocked out a lot of local hosting. [Sigh] After...

Certified or Certifiable?

As a senior technology professional, I interview a lot of candidates. I also maintain solid relationships with other folks in the community. Frequently, the topic of certifications arises: A good investment? Valuable? A clear measurement of skill? Consensus appears to draw the line related to one's seniority. If you're (for example) just out of school and looking for an instant creditability boost, by all means pursue a certification. Likely, this credential will assist you in overcoming the "junior" tag and likely land you more interviews and client roles. (Note: I'm going to use the terms senior and junior here...no offense to either. Can't think of a better one word description. I was a junior once too.) In stark contrast, the value of certifications drops off the table around the 2-3 year mark. Some in my circles even perceive certifications as a negative for the senior professional. They think, "If this guy is so solid, why is he wasting valuable...

Consulting Exodus Trend?

Is it just me or have a significant number of 'A' players left our consulting firms? People come and people go. Ours is certainly not an industry of "lifers". However, within the past year or so, I've witnessed several of my consulting peers -- the folks I really look up to -- leave the consulting arena for [predominately] full-time technology product firms. A smaller number have left for full-time positions at businesses while an even smaller number left to start their own business|firm|freelance|etc. Their departure struck me as odd because these were the type of folks who [I thought] would eventually become owner / partners at their respective firms. Certainly, the firms will carry on and continue to perform well but the departure of these folks would result in nothing less than a severe case of the hiccups and quite possibly a minor cardiac event. You know who you are. Please comment. Do we [the consulting industry] have a brain drain issue? Is this a norm...