3 ms·

I single database would require a constant internet connection and would be much slower. I aim for 0.1s feedback, and that's hard going over the network. See h

by iveqy 10y ago

I single database would require a constant internet connection and would be much slower. I aim for 0.1s feedback, and that's hard going over the network. See https://www.nngroup.com/articles/response-times-3-important-limits/ https://www.nngroup.com/articles/response-times-3-important-... I don't think it's such a bad idea for production customer data. Actually I think it's a great idea and wrote my master thesis about that: http://fileadmin.cs.lth.se/cs/Personal/lars_bendix/Teaching/Lund/Theses/Gustafsson16/final.pdf http://fileadmin.cs.lth.se/cs/Personal/lars_bendix/Teaching/... I would love to hear why you think it's a bad idea! Would you care to elaborate?

dotancohen 10y ago
I definitely agree that you should continue to use sqlite as a local cache and read from it for initial display. But I believe that on save writing back to a central server and occasionally polling it for updates would provide many benefits, the most obvious of which is decoupling the UI from the data. See my reply to self in which I mentioned a possible HTTP interface.
- iveqy 10y ago
  To get a reasonable real world working application I believe I've to do something like that. Thanks =)