Started using SQLite for building local-first apps. Thats the only valid use case I have had for using SQLite
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
La escalabilidad ni siquiera es estrictamente a nivel de tecnología, sino a nivel de arquitectura. Tantas estrategias que hay para eso y optan por montarse la de una Big Tech desde 0.
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
"bro, pero SQLite no escala, no sabes el problema en el que te estás metiendo" – el bro que se la pasa haciendo hora nalga en las oficinas de su consultora de confianza
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
Ummmm let’s get that limits
import pyspark…
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
deadlocks, anybody? or is it just me?
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
SQLite has some limitations and downsides in certain cases.
However, what's interesting is that most of the negative responses to this tweet come from people who seem to be afraid of simplicity, rather than those pointing out these specific cases.
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
Wrote an internal tool using SQLite. Encountered countless DBLocked exceptions rendering it useless.
Switched to a mssql db w same exact source code and ran flawlessly.
Sounds to me the problem lies in SQLite default config.
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.
A reminder to everyone that, on average, removing any and all network latency means your writes go from milliseconds to microseconds. You can stuff 10x, 100x, or up to 1000x as many writes into the same amount of time. SQLite scales
> How do you get around SQLite's write limits?
Listen, SQLite can handle thousands of writes and a ton more reads per second.
If you're hitting these limits, congratulations. You're probably very rich at this point and can hire someone, if not a team, to figure it out for you.
If you're far from these limits, and thinking about workarounds, you're probably doing something wrong.