Yet another ORM? Reducing the impact of database changes on an application
<div> The session is about domain driven development. It seems most ORM frameworks being out there do not really solve the abstraction problem between the two as these are table centric. Do such really follow SOA principles when it comes to treating the db? Empower your next project with... server side ORM. Tip: client side here is your .NET app. I will let you deeply rethink what you've done so far.</div> <div> </div> <div> My approach let me save days or weeks of otherwise wasted development hours when it comes to "make a change". You might feel ORM of your choice seem let you kickstart the project faster, but then... every major change and tweak here and there is a nightmare (refactor, recompile, retest, redeploy). Can this be done independently when introduced a db change? Nope! It always must go in sync! What if we need flexibility? I worked on projects where requirements changed so rapidly that completely rewriting an app after every change is like working one step forward, two step backwards.</div> <div> </div> <div> This will be presentation with lot of practical examples on how to mitigate the risk of breaking the app and you may like following me. Most of the people I did talk to did not know about it!</div>
Rajmund Rzepecki
XML | ORM | Database | .NET | SQL
Mobile Home
Sessions
Schedule
Presenters
Rooms
Login