Multi-tier App = UniDAC + EntityDAC + DataSnap ?
Posted: Sun 30 Mar 2014 13:06
Hello.
I intend to create new multi-tier database applications using these three data frameworks (UniDAC + EntityDAC + DataSnap), but I'm not sure if this is "ideal" combination of technologies. Please help me decide and discuss the pros and cons or alternatives.
So I need to:
- have clear architecture and simple code (no code/tier duplications, max reuse of objects)
- use ORM whenever it is possible (on the server surely, but if possible on the client too)
- have (default) support for visual data editing, sorting, filtering, etc., via DBGrids
- mid-to-high performance and reliability (LAN/WAN usage)
- transaction durability
- I will NOT use stored procedures and triggers (data changes/requests will be handled only by ORM)
- I will USE autoincrements (identities)
I have standard expertise in UniDAC/SDAC/ODAC and in remoting (RemObjects SDK).
I have NO expertise in ORM and DataSnap (but DataSnap looks more simple then RO SDK). If it will make sense, DataSnap may be altered to RO SDK, but not to DataAbstract (RO SDK is just a pure remoting, but RO DataAbstract is complete remote dataset solution, which I don't want to use since it seems to double some ORM functionality in EntityDAC).
I am a big fan of Devart and RemObjects, but I have no problems using native Delphi technologies (Enterprise edition).
Thank you so much for discussion and tips.
Regards,
Peter.
I intend to create new multi-tier database applications using these three data frameworks (UniDAC + EntityDAC + DataSnap), but I'm not sure if this is "ideal" combination of technologies. Please help me decide and discuss the pros and cons or alternatives.
So I need to:
- have clear architecture and simple code (no code/tier duplications, max reuse of objects)
- use ORM whenever it is possible (on the server surely, but if possible on the client too)
- have (default) support for visual data editing, sorting, filtering, etc., via DBGrids
- mid-to-high performance and reliability (LAN/WAN usage)
- transaction durability
- I will NOT use stored procedures and triggers (data changes/requests will be handled only by ORM)
- I will USE autoincrements (identities)
I have standard expertise in UniDAC/SDAC/ODAC and in remoting (RemObjects SDK).
I have NO expertise in ORM and DataSnap (but DataSnap looks more simple then RO SDK). If it will make sense, DataSnap may be altered to RO SDK, but not to DataAbstract (RO SDK is just a pure remoting, but RO DataAbstract is complete remote dataset solution, which I don't want to use since it seems to double some ORM functionality in EntityDAC).
I am a big fan of Devart and RemObjects, but I have no problems using native Delphi technologies (Enterprise edition).
Thank you so much for discussion and tips.
Regards,
Peter.