4 ms·
Use sqlite3 until you actually cannot. It sounds like you're assuming it's bad, but it sounds ideal for your use-case since it is designed to be a fully-local d
by MatthiasPortzel 2y ago
Use sqlite3 until you actually cannot. It sounds like you're assuming it's bad, but it sounds ideal for your use-case since it is designed to be a fully-local database.
- tcsenpai 2y agoI actually cannot, I have severe performance degradation when I scale the blockchain over two nodes and I traced that back to sqlite 3 unfortunately
- MatthiasPortzel 2y agoIf each node has its own local database, then: * you shouldn’t need a database that can handle concurrent writes * and increasing the number of nodes shouldn’t increase the database load