3 ms·
I've seen folks approach things this way -- Dr. Nic's done some of it in an exploratory manner: http://tinyurl.com/36twmo http://tinyurl.com/36twmo But I don't
by sanj 18y ago
I've seen folks approach things this way -- Dr. Nic's done some of it in an exploratory manner: http://tinyurl.com/36twmo http://tinyurl.com/36twmo
But I don't think it is the best approach. I'd much rather push ALL of the magic down into the database layer and not have the app worry about it at all. I want ONE layer of magic and I'd prefer it to be in the DB, where it seems it "should" be.
- cstejerean 18y agoI'd rather have the layer of magic be in the part of the code I understand best so I can fix it when things go wrong.
- sanj 18y agoI'm pretty confident I can learn what I need about DB configs, so I'm more concerned about it being in the "right" place from a complexity and efficiency standpoint.
- j2d2 18y agoWhy doesn't anyone ever talk about distributed caches? Is it really necessary to hit the database for all data? Perhaps I'm confused...