sql server - What is a good approach for migrating from LINQ to SQL to DocumentDB? -


first, little background our situation. several years ago started asp.net mvc project using linq sql dal. being developer on project @ time, chose use because pretty supported in community , needed focus more on application logic , ui design market. strategy worked out quite us.

it wasn't long, though, until needed write multi-threaded code in windows service against same data store. linq sql encountered sorts of problems crossing threads. still being developer @ time , needing service quickly, resorted duplicating enough of dal , models using pocos , enterprise library. though not ideal architecture duplicate models , dal functionality, worked enough , got me through.

that 5 years ago. we've been successful our project point success liability not linq or enterprise library, sql itself. now, before suggests give our sql database overhaul indexes , of that, have done that. added dba on contract , solved problem us. performance restored , things okay. problem, though requires (in our opinion) frequent maintenance our business model , requirements.

thankfully, microsoft has stepped game azure services. of specific interest (we have 2 developers now), documentdb. in sql have several large, flat, busy tables give areas of our application severe performance problems when start approach need db maintenance. don't have resources devote ongoing maintenance. we've decided move our application either in part or entirely documentdb. few proof of concept demos internally tell move type of application have.

if you've read far, thank you, , here question. way migrate linq sql classes , generated logic dal backed documentdb? thankfully, had foresight on use irepository approach such application won't impacted, @ all. i'm concerned of "magic" crud stuff linq sql design surface coded me. other developer , understand how write our own dal code, need quick , consistent approach takes account behavior application coded expect having been backed linq sql.

my instinct unwind of generated code linq sql did me 5 years ago , divorce linq sql designer, add in our own dal via di , go there. other developer more advanced on part of things, have pretty decent amount of confidence can done. hoping out there can avoid pitfalls can done efficiently.

as david makogon points out in comment, question has no "correct" answer broad , opinion-based. i'm getting broad range of suggestions, nothing consider definitive answer.


Comments

Popular posts from this blog

Email notification in google apps script -

c++ - Difference between pre and post decrement in recursive function argument -

javascript - IE11 incompatibility with jQuery's 'readonly'? -