Recently, I was met with some friction by the IT department at a client where, they asserted, that a decision had been made years ago to ban Entity Framework. Like many enterprise environments, this client was understandably concerned with the potential pitfalls of embracing Entity Framework. That meant that my job was to convince them otherwise – not to discount their apprehension, but quite the contrary – to demonstrate how EF can be leveraged for its advantages, and avoided for its shortcomings.
Entity Framework (EF) is a broad framework with many optional parts. There are several aspects of EF that provide great benefit, while others are a source of great consternation – particularly from the perspective of the database purist. As the cliché goes, “with great power comes great responsibility,” and so this blog post explores different aspects of EF, and…
I was doing some comparative analysis on some of the libraries in Apache Spark when I stumbled upon this project, CodeFlower by fzianinotto. It represents source code visually by graphing each source file, linking them by their directory and dependency structure, sizing them by count of lines of code, and coloring them accordingly. The images are sized proportionately.
So I took a look at the two versions of Entity Framework that the DotNet team at Microsoft has been supporting and visualized them.
They probably make nice wall posters.
Entity Framework Core
Entity Framework 6
To learn more on how Tallan can transform your data into actionable insights and help you capitalize on business opportunities, CLICK HERE.