addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Dapper, Rise of the MicroORM with Rudy Lacovara

Most of us have some experience with full on ORMs like EF4 and NHibernate. If you've ever worked with these ORMs and found yourself thinking "This would be so easy if I was just using straight SQL" or "Why did I just waste half my day troubleshooting an error that the DataContext hid from me?" then you might like Dapper. Dapper was developed by those StackExchange guys to handle the parts of StackOverflow where fine grained control over the SQL and performance were an issue. It's an example of a new style of data access known as MicroORM and it's kind of awesome.

We'll go over how to use Dapper, talk about the architectural decisions it encourages, and then take a look at how I'm using Dapper is in a real world application.

 

Rudy Lacovara is the Founder of HireFlo (http://hireflo.com) and a .Net consultant working in the Boulder, Colorado area. Robert Martin and Itzik Ben-Gan are my heroes. He thinks that DDD and ASP.Net MVC are huge steps in the right direction, he cried when he heard that Phil Haack left Microsoft, and some day he hopes to be one of the cool kids and use git.

 

Join or login to comment.

  • Stan S.

    Rudy you did great with explaining your experiences building the plumbing for data access. Thank you for showing us a microORM Dapper.

    August 24, 2012

  • Ely L.

    The talk was eye opening on a different take of data access technologies. I liked the simplicity and speed of Dapper, but not so sure I want to give up Linq and other features of a full fledge ORM for most of my apps. I could see using Dapper on a client project that won't use an traditional ORM or a quick app.

    August 22, 2012

  • John B.

    Nice Job Rudy!

    August 22, 2012

20 went

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy