What an outstandingly excellent explaination !!! Yes handling mutexes and semaphores has it's own throughput headaches
@AsliEngineering4 ай бұрын
Thanks!
@rktpro6 ай бұрын
Every embedded systems guy who works with C would find the 'single thread' design just another day in life.
@rohandvivedi3 ай бұрын
RTOS ?
@kommisettyveerendranath532 жыл бұрын
Thank you Arpit, very nice way of explaining the whole concept behind the redis single threaded model.
@sahajarora21623 ай бұрын
Beautifully explained. Thank you!
@vikrantkumar4431 Жыл бұрын
I used sorted redis sets in my company project for leaderBoard 😅, completely removing db here. Fetched the leaderboard combining two scores into one
@sw90383 ай бұрын
Redis is no longer open source now. Can we use redis community version for commercial websites now? What is the impact of changing the licensing policy for the Redis? Is it only for cloud support? What can I do with my existing redis integrated projects? How Valkey is substitution for Redis? Could you please make a detailed video on this?
@AsliEngineering3 ай бұрын
You can continue using it. It just prevents other companies from offering it as a managed service. No changes on your side.
@sw90383 ай бұрын
@@AsliEngineering Ok thanks.
@kalpeshmali84982 жыл бұрын
Itni deep me reddis padai hai aapne sir thank you very much sir ❤️🔥🙏🙏🙏🙏
@tejpalkhachane1965 Жыл бұрын
Pls add some videos on api performance improvements, error handling in micro services, performance testing of micro services
@jasonngan5747 Жыл бұрын
Very great and thorough content! Thanks for the nice work!
@jivanmainali17422 жыл бұрын
Network IO is slow but execution is fast (in memory ) implies it has no waiting data (queue of commands ) to process thus IO multiplexing seems to be a wonderful solution
@jivanmainali17422 жыл бұрын
Hi Arpit , Is there a way we can limit number of tcp connection to redis at application layer in synchronous way ?
@sakshamjain162 жыл бұрын
Use Redis pool to limit connection
@liveforothers1846 Жыл бұрын
@arpit as you said redis create connection fromTCP and in a single thread all those connection comes and execute. But i have also seen i can only create one connection in redis and that one connection can also serve as many request as multiple connection does. Which is more scaleble single connection with multiple request or connection per request is the ideal practice
@chetansharma5514 Жыл бұрын
@Asli Engineering :- I like the content of your playlist. Request you to make a series on Object storage technology ( a detailed one which covers the internal such as how the data is organised and stored on physical hardware ) .. I have been searching internet for this details but have not found anything so any kind of help would be highly appreciated.
@amitdahiya8969 Жыл бұрын
You can go through the book : operating system concepts, it covers Process Management, Memrory management and storage management
@kaushikdas417 Жыл бұрын
So the event loop thread is always busy, always checking if something is there to work on?
@AsliEngineering Жыл бұрын
it is not a separate thread.
@jivanmainali17422 жыл бұрын
Also what happens when you have data from multiple socket at a same time ,when you read? @18:00
@AshokBathini Жыл бұрын
Not sure if redis uses epoll; I guess it may be using it. If u use epoll, u need to register fds(sockets) with it and whenever any related socket buffer is full, u get a handle on all those fds, process them sequentially and go back and ask for more fds whose buffer is full/ready to read.
@sergioliberati91929 ай бұрын
this is a really good explanation 👍👍👍
@vaibhaves2 жыл бұрын
Any discount for college students? :D
@MsTendawa Жыл бұрын
every operation is atomic in nature, then how it behaves when the redis in reactive driver (reactive nature)?
@cnkumar202 ай бұрын
having worked with asyncio of python lib, made total sense. (python is also single process due to GIL)
@pechimuthu.j7953 Жыл бұрын
I have a query, how this eventloop works in multi core machines. Blocking calls issue is addressed because of event loop I agree but how we will achive parrallesim with multiplecore
@AsliEngineering Жыл бұрын
It does not work on multi-core
@AshokBathini Жыл бұрын
We have worked on something similar, built our own webserver using epoll systemcall. We just create a separate process per core.
@nitishagrahari9943 Жыл бұрын
This channel should gain more reach ❣
@vineet49916 ай бұрын
Hi Arpit, there will be concurrency issues if we have multiple shards/nodes of same redis instance? Since they both work separately even after being single threaded???
@Jollyrogger8053 ай бұрын
If you are referring to redis cluster, redis network io will still be single threaded thus no concurrency issue
@akashanand37838 ай бұрын
Very well explained. Thanks a ton😊
@thenerdycoder075 ай бұрын
Please do internals of kubernetes
@sumitpatnaik70572 жыл бұрын
Sir it might be cringe but i am binge watching for weekend as series 😅 really good content Thanks
@AsliEngineering2 жыл бұрын
Means a ton 🙏
@hackwithharsha2 жыл бұрын
Hi Arpit, Thank You !! Do I have access to course for life time once i purchase it and also can i do it in python while watching in go lang ?
@AsliEngineering2 жыл бұрын
Yes. Lifetime access to the course.
@hackwithharsha2 жыл бұрын
@@AsliEngineering Thank You !!
@大盗江南7 ай бұрын
amazing content!!! Thank you!!!
@StrawHatLuffy7502 жыл бұрын
Nice you are a great teacher :) i am planning on getting the redis internals but the cost is a bit high😅😅. hopefully would buy it sometime.. will there be more sessions on redis internals??
@AsliEngineering2 жыл бұрын
Thanks a ton! Redis videos will not be on KZbin. Have covered them in my course.
@Ady-ny1gz2 жыл бұрын
Hey @arpit, thanks for the excellet explanation, appreciate the efforts 🙌🏻 one ques - what iPad app are you using for explaining? it looks very neat, gonna use it for personal uses.
@AsliEngineering2 жыл бұрын
Goodnotes
@madhulikaghosh38762 ай бұрын
Very very nice.
@subee1285 ай бұрын
thanks
@carlosluque4753 Жыл бұрын
I am finding these videos so interesting! I'd love you ever make a video like these ones about how HFTS (High Frequency Trading Systems/Applications) work and especially all the optimisations required to achieve processing time in the order of microseconds or nanoseconds. Not sure if it is your area of expertise but I am sure you definitely have the knowledge for it. For example, I know that in many cases, they would avoid the use of threads to avoid waiting time in locks, data locality to take advantage of CPU L1 and L2 caches, lock free data structures, etc. Been reading a book about it recently, super interesting. HFTS is a super interesting topic, would love if you can produce some content :)
@musafirgauravv2 жыл бұрын
Redis sounds like Node to me
@AsliEngineering2 жыл бұрын
Yes. Both work on the same foundation - event loop.
@StrawHatLuffy7502 жыл бұрын
Please make paid series courses with other open source softwares :) in golang
@AsliEngineering2 жыл бұрын
Suggest something, I am open for anything and everything.