I would truly appreciate a homelab setup from you, love your videos, God Speed!

Be aware that in AOF (Append Only File) persistence, Redis saves logs every second by default, not every write.

Perfect example for: Just because we can doesn't mean we should. But content wise this video is top notch

Amazing work! Not only the editing and presentation which is always so delightful, the idea itself of using Redis as a database and the persistency concerns are perfectly explained. THANK YOU!

Next video idea: most people scoff at the idea of using filesystem as a database, but did you know we can recreate Postgres with fs in c++ and achieve similar functionality and safety

Hey! Nice one! Online Engineering Lead at Ubisoft here... Sorted Sets in Redis are the go-to solution to do leaderboards in the game industry actually, but you're constantly optimizing to battle server costs since everything stays in memory, and larger leaderboards need machines with more memory, which happen to be more expensive. But honestly, as soon as you want persistence and you enable AOF for every write operation, you'll start to run into performance issues on Redis too. There's no magic bullet in engineering - weigh the pros and cons for each use-case and then choose the tool.

Dedicated HomeLab pls

You are really great at this. Your explanations are concise and clear. The pacing is perfect. The editing is quite good.

In my past experiments with using redis as a primary store it tended to not scale well once the project grew to a certain level of use and complexity. I often use it as a primary store for specific slices of a given application's data persistence strategy when and where it provides advantages over a traditional RDB. Inserts when using a RDB tend to be expensive (especially if the table has a bunch of indices) so Redis can really shine in very write heavy areas of your app like messaging, sensor data capture, etc.

Really enjoyed this. It was cool to see the reasoning behind certain redis features. Thanks!

This made me appreciate SQL more. Look what they need to mimic a fraction of SQL power

You've been doing great. The content is presented at a reasonable speed, well at least for me. And the content its self has been very interesting and informative. Personally, I'm really interested to hear about your home lab, so please do an overview of it and maybe down the line a deep dive ;-) Thanks again, bud!

Can confirm: you were using redis the right way at the start. Enjoyed watching this but wowzer, I can't imagine inheriting a project setup this way...

Definitely interested in your setup :P - thanks for the hard work on this content!

So instead of using postgres I can use redis and recreate most of the SQL functionality myself, with less safety and more complexity and space for error... I struggle to see why to use this in any real world setting. Even for side projects, if I wanna set something up quickly, I don't wanna have to have to create indexing etc myself before being able to develop the app. I'd also be interested how the performance actually plays out once you start parsing long JSONs, maybe it will still be faster, but it's something you didn't consider. Also if you eventually decide to switch to postgres that could be a really hard rewrite.

straightforward, well written, clear and simple videos, love them!

Wow. Just wow. You totally delivered, forwarded this to my colleagues.

Great insights, thank you!

I just started working on backend and we have a fairly complex setup. This video dropped just in time. Not only this tells you what redis can do or can't but is a small primer to starting with redis. Top content.

Such high-quality content we need more content like this on yt

I was already using redis as a primary database, so seeing this video cheered me up!

You missed a key point. During snapshot redis will fork the process and dump what is in that forked process to disk. This means you need 2x the ram to perform this action but also it’s a global db lock during the forking process. If you have a small dataset this generally fine but if you have a large db this process will cause large spikes in latency when the snapshot begins.

Beautiful editing

High quality content thanks Dreams of Code.

+1 For the homelab setup video!

You don’t need a cache if your database has enough memory. You don’t need a database if your cache has enough disk space. You don’t need any of them if you have no users.

Great video. Thanks

Great content! Subbed.

Awesome work! Thanks! Please also do a seperate tutorial for "Python and Redis Queues"

I think you've convinced me to stick with RDBMS + SQL as the primary database for my relational data 😁

Totally agree with the video, the biggest drawback is the lack of higher level primitives but in some cases it's indeed worth implementing them yourself on top of redis. The company I work for had a chat system as part of our django + postgresql api that could handle around 1k messages per second before it started chocking up (can't remember the exact numbers, it's been years). Partly because of django websocket implementation and partly because of the database model designs, they could have been optimized further but the performance would have still been far from ideal. We reimplemented it as a nodejs microservice with redis as main database and based on tests a single instance could easily handle 10k+ messages per second, no specific optimizations just from switching language and database. After deploying to production it has never gotten high enough real world load to use more than a fraction of a single cpu core in the cluster.

So now I know that I *could* sort of replicate a relational-ish storage model in Redis by reimplementing abstractions that are already in place in any RDBMS by hand at a lower abstraction level. Which is indeed quite interesting. The question is: Why should I, instead of just using an RDBMS?

I see some usecases in which you could use redis as you said, but for me the main drawback is data consistency. Having a very well defined schema of your data and the responsability of shaping it right makes things way more maintanable. That s my personal problem in general with nosql

Your videos are amazing. So clear and well-paced. This is the first one of yours that ive come across. Definitely subscribing. Do you use after effects for all your anims?

ayyeee congrats getting a home lab set up that's sick!!

Really good introduction to Redis! Huge thank you! I see you're a man of culture as well with those DrafonBallZ and Naruto references ❤

For me, I fell in love with Redis when I had to do work on a logistics management system. Out of the blue, just reading the documentation, I found out that it has in-built geo location functionality and can easily determine the straight line distance between two points, accounting for the curvature of the earth (correct me if I'm wrong, but I believe under the hood, it uses the Great Circle function). Thanks for the vid.

I can't believe how quick you made a 21 minute video about Redis feel. Great video

Great video 👍

interesting with your terminal, can you share what theme did you used? 2:23

I've already been using it as a primary database. Our data is very small and most of it is non-persistent (status hash tables that expire after 30 days). But we do keep record of transactions, which is an integer timestamp and a simple 41 character id string. I also commit an apparent faux pas, and I use the Logical DB set to organize my data. Apparently it's an anti-pattern because some people may implicitly think they're actually separate systems when they're not. But that doesn't really matter since the way I use them as almost like folders to help organize my data.

nice video and good explantion

Absolute great video, I can't thank enough 🙏 sir you are a master jedi in redis ...P/S your tom bombadil part caught my eyes :)

Thank you for this video, you tought me some new things about Redis! Did you leave out Redis JSON on purpose, because it's an awesome feature; it allows for storing JSON documents as values, and creating indexes on the actual JSON content. We're using it in our CQRS setup, both as message store as well as the Query model.

What's the autocomplete/hint plugin you are using? It seems great.

Would like to see your video on your homelab. Was there any already? Or would be? Thanks!

this is informative, thanks a ton

Dedicated HomeLab channel?!? Yes, please

@Dreams of Code , How would you classify a data base to be small or big? what if my writes to database is for 20,000 users with around 3000 concurrent requests to DB, Will Redis be ok in this scenario or Postgres might work out better? I will definitely go for a regression testing in both as the project itself is small - but still would like to know everyone's perspective as well.

Great! Would love one like it on redis-stack please!

Was using redis as my primary database, but still learned a lot from watching this

This 20 minute video taught me so much more than all the other redis videos on the internet, thanks ❤

At this point, I would like to see a video on how you make your KZfaq videos. Very clean and interesting. Please make a video on how you achieve this including all the fun and interesting animations. Thanks

I am very interested in your updated Home Lab Setup, please do a video or post about it.😀

Definitely do a home lab setup tutorial!

For personal projects I use IndexedDB and then I sync it to sqlite on the back end. With everything on the front end it makes it super simple to have things nice and speedy. Granted, I don't need to worry about live data this way. So, it isn't a good model for all apps.

I always wondered what Redis was used for, this is a great video to go from zero to having some clue.

Our company uses Redis as a runtime database for our live chat system, and it saves off transcripts into a real RDB at various checkpoints. The footprint in redis for all of that is 400MB, and we saved an immense amount of maintenance/development cost doing it this way..

If Redis supported disk only keys, I'd consider this once in a while. It's really nice!

Great vid man? Whats the zsh plugin you use to show the argumentos for every command? Or is ot just redis? Thanks!

Don't the Redis OM libraries take care of the first drawback you mentioned?

I use it to lock out a request across multiple instances of an app. Where money and transactions are completed, I couldn’t have a user start more than one thread across multiple apps, so it’s GREAT to lock out that process single file by user

DBZ fan! Nice video! Very well explained.

Good to know. Sometimes you just happen to have a redis instance and need a minimum of database functionality. In my former job I implimented a caching service, were the invalidation logic was very complex I ended up implimenting it in postgres, but we allready had a redis instance for caching auth sessions, so I could have done it there as well.

5:04 I am really tempted to migrate one of my projecrts to redis. At the moment it's running on RaspberryPi as a MariaDB table. It's 22 fields wide, 400k of rows. Normal updates are simple, a piece of code grabs the data from API, processes it and updates the table. Then the data is represented through Metabase which really stresses Pi's I/O, especially when I do manual improvements of the data (e.g. update all records where a field matches a regex, that triggers massive updates). Having it in memory would make the experience so much nicer.

Using Redis for a db is similar to using MongoDb or any key/value NoSql database. You outlined the cons quite well but addressed them with Redis datatypes and transactions. I think the big pro to using Redis as a NoSql database is the simplicity if one has a use case that doesn’t need complex querying. This is referred to as impedance mismatch I believe, where the dataset your UI + API match that of the database.

If I had to chose a favorite DB of any kind it would probably be redis. I also recommend anyone to build a simple crud app only using redis as the database and implementing all the operations with that. It’ll teach you so much about structuring data and how to query it.

Has noone made something like an SQL to REDIS compatibility layer? So I have a "create table" command and it does the appropriate steps for that in redis for me?

amazing video

I’m reminded off the scene in Jurassic Park when Ian Malcolm says ‘Just because you can, doesn’t mean you should’. Or something like that.

Such a healing rendition .

I wouldn't recommend redis as a sole prod DB because as you said volatile memory is expensive and you did not touch on redundancy. So in addition to dealing with structuring all the data, composing the indexes, and so on - which is the fun part - you will need to also learn redis sentinel and redis cluster - the not so fun devops piece - in case your redis master goes down. Slaves will have to be promoted and properly synced, and if that process is not well understood / configured correctly you are in for a world of hurt. Also having 2-3 slaves running for a single master will 2-3x your costs. However it may be possible to justify some of the costs by setting the slaves as read-only to aid in throughput.

I use tarantool, can support SQL, have append only file also, can store more than ram if using vinyl engine (not the default memtx engine) the gotchas is that no date data type (so i use epoch/timestamp without timezone), and the table/column name all capitalized so if you create table with lowercase/mixed-case you must quote it on query so can overcome all redis limitation.

Would love to see the homelab setup

Please talk about use cases for redis and memory constraints or expectations per case load

Mindblowing

Awesome I didn't understand half of what you said😅 Will rewatch it again 😅😅 Thanks for the content 😊

I would like to see performance and ease of use compared to an in-memory SQLite database To see if the ACID Compliance and the SQL features comes at cost, for the dev or the runtime speed

Alright, I'll try it for the project I'm working. If this fails we'll be back with our pitchforks

Homelab video please. I have a homelab setup and would love to see yours!

this is a great video, i hope redis doesn't change its license to a non-open source license

It might be good to add that redis transactions are not nearly as powerful as SQL transactions. You can resort to using LUA scripts to fix that but this is really annoying to maintain and to write proper tests for.

I only use it for sessions. Works well especially for storing OAuth flow acces tokens

what theme/setup do you use for your terminal? it's very pretty

Nice I like REDIS but there is a lot to manage and that is a lot of data sets, a normal DB lets me abstract this away with table index magic and in this case I might as well just use python/TCL/C++ with hahses, sets and arrays (though TCL will let me push raw commands in avoiding the need for an API) and write every transaction to a rotating log file with a threaded snapshot by time.

the best video I watched today!

I used redis as a database for location data which on moving object is ephemeral my default. Then the geospatial store was super usefull finding objects that are closeby

Very good and informative video, thank you. As a user of Postgresql since 2001, you are missing the biggest and most important feature of RDBMS -> data and reference integrity. This is unachievable by redis or any other nosql solution. Of course, if you have complex data models and you have the need and skills to write good SQL, redis falls short big time. (CTEs, Window functions, triggers, aggregates, etc) But if you are building something really simple or without structure, redis is great.

1:47 Exactly! Please create video on setting up homelab. By the way, I have only single laptop. :)

What I would have really enjoyed would be comparisons to something like Postgres. When does Redis perform better, when Postgres?

I have one stupid question. What if I store data inside of my go app? Inside of some map structure. I know about data loss if the app restarts. I’m curious about efficiency. Is it faster using Redis?

Great video. I'm convinced Redis is only good for the caching layer.

you should also cover the redis extensions. they're great

I think if you need a very high throughput for read/write operations, sure. But making redis a drop in replacement for something like postgres or mongo db.. It's not the same tool, it wasn't really designed to do the things you are suggesting so I feel you are trying to force a square peg in a round hole.

Video about your linux dist setup and terminal setup? And I wait also video about Rust Tauri and Rust Yew

I did read redis docs before but your video explained it so well i made parts of my software 30%ish faster and i take that!

0:01 not anymore 🥲

how to do create presentation like this?

The awesome bomb you threw was *"dont use KEY" in production unless you're debugging, it's slow and blocking* . I seriously didn't know that. I searched it up and it is absolutely true.

@Dreams of Code Hi, you're using mac os for this or ?