🏒 Lucian Marin I will definitely use Redis for my next project. I don't want to touch a database any longer. Sublevel will remain my only SQL oriented project. I will rather build complex structures and change them using procedures than figuring out that's the best path to access data using SQL. You can find a great introduction to Redis at matt.sh/what-is-redis written by Matt Stancliff.

Haaktu I'm wondering what lead to this decision. I'm partial to non-SQL (or is it noSQL) solutions for my personal projects.

🏒 Lucian Marin SQL is the main bottleneck on Sublevel. Instead of planning new features, I'm tweaking the Postgres query planner. It's very hard to maintain a certain level of performance with SQL. Let's say you want all requests to be loaded in exact same amount of time. You can't do that. Each SQL query is different and they might behave differently under heavy load. I doubt NoSQL is any different. That's why a key-value store like Redis is perfect for high performance applications. You know in advance what's the performance for each value stored, so you can plan features as you write code.

👽 Paul Webb Will you ever rewrite Sublevel to use Redis and then port everything over? Maybe take the site offline for an hour and bring it back with the new hotness!

🏒 Lucian Marin That will be an interesting project. But right now I'm working on an update that will optimize the SQL queries speed in each page. If everything goes as planned, I'll deploy the new code this weekend.