Azure Hadoop and Entity Framework -


i stating new project needs portable , in scenarios have 100's millions of entities.

now azure getting hadoop of course got attention big data scenario. have small data scenario under 1 million rows.

entity framework code-first way see designing needing hadoop in mix of course may complicate things (entity framework of course been used give simpler storage providers smaller data sets)

now question have experience in mix?

can recommended if approach or not, if not there better way?

working on reasonably large system based on entity framework code first, caveats have been working ef4 , cannot upgrade 5, mileage may vary , outcomes going affected intend do, experience has been ef doesn't handle large amounts of data tremendously well, quite inflexible, if need change standard behaviour in way there chance going end having hack nasty workarounds, , performance isn't amazing. if want things aren't things ef expects do, can run walls.

if thinking of designing relatively simple/small scale asp.net mvc setup, think ef choice. larger scale operation need more flexibility or planning go beyond basic operations might find nhibernate works better. don't have experience that, colleagues have worked both tend prefer nhibernate. ( brief article on comparison - bit old ef has addressed some, not of points there. different design of course. )

it may more high-traffic or unusual stuff need roll own data access anyway achieve right performance or able find right data. unsquestionably, if planning try working ef recommend serious prototyping ensure can need.


Comments

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

keyboard - Smiles and long press feature in Android -

node.js - Bad Request - node js ajax post -