1,184 karma · joined February 21, 2023
datadeft.at.hn
What a progress we have with these. Amazing times.
Using popularity as justification of anything is the definition of slippery slope.
Redis does not natively scale across multiple cores in a traditional multi-threaded sense, you can still scale it horizontally (across multiple machines or instances).
This horizontal scaling is also problematic. Some of the cloud solutions we used would die during a scaling event.
I went on the hunt to find an alternative but not sure what to replace it with. At this stage the interface has to be Redis compatible because devs really like it.
I found this so far: https://medium.com/@shafreeck/titan-a-distributed-redis-prot...
¯\_(ツ)_/¯
It is much better if the gen pop is the sacrificial lamb.
Never heard of it and I do a lot of performance related work. Is Superluminal really that popular?
"In theory, theory and practice are the same. In practice, they are not."
NAT was used as a blocking method for all incoming connections for SOHO networks for decades.
I think most historical discoveries should be prefixed or suffixed with this because as we dig up more things we might learn that there was an even older writing system (in this case).
Examples:
- High-fructose corn syrup is eating the world. . You can fight it like so many people before, but you will lose like everyone else
- Cancer is eating the world. You can fight it like so many people before, but you will lose like everyone else
Etc.
I think bad things could be replaced with better things where we have this luxury. Taking a passive stance on this is pointless and lazy.
https://github.com/dhall-lang/dhall-kubernetes
Type safe, fat finger safe representation of your YAMLs is grossly underrated.
1. fsync, fdatasync - synchronize a file's in-core state with
storage deviceI think it stability was due to the fact of combining great technologies like LevelDB and Erlang. I wish it was a bit more popular.
I would love to see the following projects instead:
- exposing a transactional API for S3
- transactional filesystem
Accidental complexity, accidental complexity, accidental complexity and when we use a tool that is designed for problem A for a problem B it is not sufficiently dealing with complexity. This is why we need a new tool.
¯\_(ツ)_/¯