Showing Post From Open Source
Kafka and Redpanda: revisit the choice before you treat them as the same bus
Many teams say “we run Kafka” when they mean “our services talk to a Kafka-compatible broker”. That shortcut was useful when one open source broker dominated the protocol.
Read moreOpenTofu and Terraform: revisit the fork before you pick one
Many teams picked Terraform years ago and have not looked at the choice since. In August 2023 its licence changed and a fork appeared.
Read moreRedis, Valkey, and Dragonfly operations: persistence and failover
A cache becomes a database the day nobody can rebuild it. After that day, persistence and failover are not settings copied from a blog.
Read moreRedis, Valkey, and Dragonfly benchmarks: read the method first
A benchmark number without its method sounds complete, but it does not tell you what happened. The first note in this series, Redis, Valkey, or Dragonfly: revisit the choice before you treat them as the same cache, covered licences, history, data file compatibility, and cluster mode.
Read moreRedis, Valkey, or Dragonfly: revisit the choice before you treat them as the same cache
If your service already uses Redis, the name on the port has not changed. The product behind that name has. Treating Redis, Valkey, and Dragonfly as three labels for one cache is the habit worth unlearning.
Read more