Non-blocking ORM issues
Posted
by
Nikolay Fominyh
on Programmers
See other posts from Programmers
or by Nikolay Fominyh
Published on 2012-06-21T20:45:13Z
Indexed on
2012/06/22
9:22 UTC
Read the original article
Hit count: 263
Once I had question on SO, and found that there are no non-blocking ORMs for my favorite framework. I mean ORM with callback support for asynchronous retrieval. The ORM would be supplied with a callback or some such to "activate" when data has been received. Otherwise ORM needs to be split of in a separate thread to guarantee UI responsiveness.
I want to create one, but I have some questions that blocking me from starting development:
- What issues we can meet when developing ORM?
- Does word "non-blocking" before word "ORM" will dramatically increase complexity of ORM?
- Why there are not much non-blocking ORMs around?
Update: It looks, that I have to improve my question. We have solutions that already allows us to receive data in non-blocking way. And I believe that not all companies that use such solutions - using raw SQL. We want to create more generic solution, that we can reuse in future projects. What difficulties we can meet?
© Programmers or respective owner