I made these assertions against the 'out of box' use case. Meaning the use of MySQL and Redis as they come against each other without indexing.
I also believe with indexing the best relational databases can achieve is O{log n}. More of this here (databases O-notation).
While Redis is an in-memory store typically meaning your Redis store sits on the RAM of your server, therefore allowing it access to data structures adapted to memory storage. Hence why Redis can achieve O-notations such as O{1 + n/k). More of this here (How Redis claims O(1) lookup).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the article Darrel.
I have one question. With MySQL and Indexed Scan, reads and writes are not O(1)?
I made these assertions against the 'out of box' use case. Meaning the use of MySQL and Redis as they come against each other without indexing.
I also believe with indexing the best relational databases can achieve is O{log n}. More of this here (databases O-notation).
While Redis is an in-memory store typically meaning your Redis store sits on the RAM of your server, therefore allowing it access to data structures adapted to memory storage. Hence why Redis can achieve O-notations such as O{1 + n/k). More of this here (How Redis claims O(1) lookup).