In our previous article, we looked at the basic patterns needed to implement a repository. In many cases these patterns were such a thin layer around the underlying data access technology they were essentially unnecessary. However, once you have a repository in place, many new opportunities become available.
This article will focus on the basic functionality that one would find in a typical repository created with .NET. We’ll look at both general functionality and how that functionality would be implemented using three different styles of ORM: Entity Framework, Dapper, and Tortuga Chain.
In this podcast, Wes Reisz, chair of the QCon conferences in San Francisco, London and New York talks to Phil Haack, an Engineering Director at GitHub focused on software pushed mostly to the desktop. He’s shipping software like GitHub Desktop, GitHub Extensions for Visual Studio, and the Atom text editor. Phil joined GitHub in 2011 and is a prominent member of the .Net community.
Donald Knuth famously said, “We should forget about small efficiencies, say about 97% of the time”. But when faced with the other 3%, it is good to know what’s going on behind the scenes. 2
Exceptions are an integral part of working with .NET, but far too many developers don’t think about them from an API design perspective.
Containers are just around the corner for the Windows community, and this article takes a closer look at using SQL Server containers.
“This web page is slow” is a common complaint about web sites. While the web brings some desirable characteristics such as global delivery, it also brings challenges at the performance level. 2
Amel Musić demonstrates how T4 can be used to create a flexible code generator that reduces the amount of time and effort it takes to create RESTful services.
Kostiantyn Cherniavskyi looks at some of the issues surrounding the object-relation impedance mismatch and how many of them can be solved with hybrid databases such as Starcounter. 5
In April, for the second time, fsharpWorks organized the F# community survey. Over 600 developers completed the survey in 2016. The survey provides an insight into the brains of the F# community. 1
HTTP-RPC is an open-source framework for creating and accessing cross-platform polyglot RESTful web services using a convenient, RPC-like metaphor, while preserving fundamental REST principles. 3
This Virtual Panel focuses on some of the current trends in iPaaS. InfoQ has reached out to thought leaders from MuleSoft, SnapLogic and Microsoft to participate in this dialogue.