35 ms·
My cheat sheet is: For transactions, postgresql. For analytics, clickhouse. For cache, redis. For search, elasticsearch. For objects, anything s3 compatible. A
by joshxyz 6y ago
My cheat sheet is: For transactions, postgresql. For analytics, clickhouse. For cache, redis. For search, elasticsearch. For objects, anything s3 compatible.
Anything else, I really have to do in-depth research and comparisons because 1.) Each database has their own pros and cons, 2.) These pros and cons between dbs tend to overlap and has each of their own gotchas, and 3.) These pros and cons also improve overtime where some problems brought up earlier might be addressed already in the lastest releases.
CMU Database Group's YT channel is also worth checking out for introductions on some databases.
https://m.youtube.com/channel/UCHnBsf2rH-K7pn09rb3qvkA https://m.youtube.com/channel/UCHnBsf2rH-K7pn09rb3qvkA