3 ms·
Just because you can use something doesn’t mean you should use it. If you have 10k writes a second and 90k reads a second then SQLite is an awful choice.
by Closi 4y ago
Just because you can use something doesn’t mean you should use it.
If you have 10k writes a second and 90k reads a second then SQLite is an awful choice.
- kasey_junk 4y agoHave you benchmarked it? Given modern commodity servers and no network overhead I’d buy it not being a problem. My intuition is you are right but given the operational simplicity improvements it would be worth exploring.
- hedora 4y agoThis. Like I said, postgres or mysql are probably better choices. However, modern hardware (especially small sync disk writes) is really fast,and sqlite has its own strong points.