4 ms·
Ok, that's a fair point. I feel like I have the skills to handle that, or to create redundancy if necessary for reliability, so that doesn't bother me, but I c
by sea6ear 10y ago
Ok, that's a fair point.
I feel like I have the skills to handle that, or to create redundancy if necessary for reliability, so that doesn't bother me, but I can see the appeal of ignoring all of that.
I still like the idea that I'm not trusting a "black box" to run my code. I know how it's set up and what it's doing. And if I add replication or load balancing, I also understand what's actually happening there. But you're right, once you get to that level, you're out of the realm of "simple".
Maybe I can still hide behind my earlier comment "unless you need the scalability..." to say that covered your caveats, but I'll admit I wasn't explicit about the considerations that guide the optimal use cases.