Just because I think SQLite works great for Joy of Rails doesn’t mean it’s right for you. You may be wondering:
"Is SQLite a good fit for my next Rails app?"
I’ve set out to help you answer that question here:
https://joyofrails.com/articles/what-you-need-to-know-about-sqlite
#sqlite #rails
"Is SQLite a good fit for my next Rails app?"
I’ve set out to help you answer that question here:
https://joyofrails.com/articles/what-you-need-to-know-about-sqlite
#sqlite #rails
Comments
Seems like sqlite is perfect for projects that def won’t ever need to scale horizontally.
Otherwise, still seems simpler to me to use postgres/mysql even if it’s on a single node. Similar benefits and easy to scale if needed without distributed systems headaches.
For the typical app I think you just end up (badly) reimplementing postgres once you realize you need read-after-write consistency or transactions.
First rule of distributed systems is… 😀
Step 1 was https://github.com/sparklemotion/sqlite3-ruby/pull/586
So that already unlocks usage like:
development:
adapter: sqlite3
database: ...
extensions:
- <%= SQLean::UUID.to_path %>
development:
adapter: sqlite3
database: ...
extensions:
- SQLean::UUID
Here's the Rails PR!
https://github.com/rails/rails/pull/53827