Devlog #11- How to make your DB fast by using Caching

[@bommuu3524]

At one place gave the full clarity on the cache. Thanks for your efforts

[@superthread_devlog]

My pleasure

[@shis10]

Amazing video.🙌🏻💯

[@bluex217]

What is the difference between "write" and "hydrate" used by the write through and write behind caches? Those 2 diagrams look the same otherwise and I'm guessing the difference is that 1 hosts the cache && DB on separate machines

[@superthread_devlog]

Sorry about the late reply, I just noticed this comment. Hydrate means you pull the data from DB into RAM so next time someone tries to pull the record, they go straight to RAM without the need query the actual DB.

[@misluyu]

finally found this!

[@superthread_devlog]

Hope you find it useful.

[@ketchupparty9997]

Nice video

[@superthread_devlog]

Thanks

[@jorisjansen2892]

Hi David,
This concept looks very interesting, I'm only familiar with the "regular" way of caching. I can't really find any examples or more in detail explanations on the internet about how to implement the other cases. Do you have any good resources for that?
By the way, I love the tech stack that you choose! But, I couldn't figure out which platform you choose for Mobile development?
And my last question, how are the open positions for developors doing at the moment?
Cheers

[@kimjong-un8543]

for more use cases look up redis
they most likely used pwa for mobile development
and the positions are open as per their website :)

[@krishnakrishna417]

Thanks very high quality content. What is the drawing tool you used

[@superthread_devlog]

Miro.

[@saravninja]

Thanks for explanation; whether Cache is referred as SRAM or DRAM?

[@superthread_devlog]

Broadly speaking it means RAM.

[@wilbertdune]

how did you write this in GO lang? thanks

[@superthread_devlog]

Go is a pretty nice language once you get going with it :-)