Readit News logoReadit News
Lio · a year ago
Wow! The performance benchmarks against redis are very interesting.

Considering that Rails 8 gives you Progressive Web Apps out of the box, this is a very competitive setup for a small team.

https://github.com/oldmoe/litestack/blob/master/BENCHMARKS.m...

hipadev23 · a year ago
I think this speaks more to a fundamental issue in ruby’s default redis. How is it only able to do 4k/s sets?
otikik · a year ago
Relevant: Just Use Postgres for Everything [1]

[1]: https://www.amazingcto.com/postgres-for-everything/

husam212 · a year ago
Using Postgres is becoming easier with the new Rails Solid [Queue, Cable, Cache] stuff.
datadrivenangel · a year ago
And DuckDB's Postgres Extension / Postgres's DuckDB extension!

https://duckdb.org/docs/extensions/postgres.html / https://github.com/duckdb/pg_duckdb

barefootford · a year ago
This gem is a really nice all-in-one setup! \n (Also worth noting that Rails 8 now supports sqlite for your application database (no more warnings about using it in prod), job queue (active job/solid queue) and cache (solid cache) out of the box.)
axelthegerman · a year ago
THIS!

Litestack seems great and probably partially paved the way for similar functionality directly in Rails 8 with the new solid* gems.

Those plus litestream are a treat

hiharryhere · a year ago
I’ve used this for a side project. Coupled with Litestream for backups it’s awesome.

I would 100% recommend.

nehalem · a year ago
This looks great!

Is anyone familiar with something similar for Python in general and Django in particular?

drchaim · a year ago
also interested!
freen · a year ago
Main-Main Replication: LiteFS

Streaming Backups: LiteStream

Just missing logs and, well, for me, graph database.

tillcarlos · a year ago
Yeah I used the full litestack (and litestream for backups) for my SaaS. Oldmoe is also auper helpful on twitter.

Once Rails 8 came out I switched it all over to the solid* gems which pretty much did the same thing.

Sqlite is awesome in the beginning, especially as there are no extra services to start (I only have a web process and a jobs process), all is sqlite.

Sometimes there are db locking issues (using blazer gem, so I guess that uses a different adapter), and I had to optimize some queries. But that’s about it. The SaaS processes thousands of job daily (mission control gem is awesome) and stable so far.

At one point our DB grew to 16GB because I stored all Api requests. Even then it was still fast (except queries on that api requests table).

Running four sqlites definitely saved me some time which I could use for customer focused things. Highly recommend for MVPs, probably more.

androiddrew · a year ago
I wish there was a Python project like this