Andy
Andy @ldehai ·
纯 Go实现的轻量级的分布式消息队列 miKago 🚀。 没有 JVM,抛弃 ZooKeeper,完全依赖内置的 Raft 算法手搓共识集群; 支持原汁原味的 Kafka 客户端二进制协议、Segment 磁盘稀疏索引,并打通底层 sendfile 实现了真正的 Zero-Copy 零拷贝下发!#Golang #Kafka #DistributedSystem⚡️ 代码如下github.com/ldehai/miKagoU
241
InfoQ
InfoQ @InfoQ ·
What are the 3 fundamental ideas every dev should know if they're unfortunate enough to work on a #DistributedSystem? @samnewman breaks down the essentials: 1️⃣ Timeouts – giving up 2️⃣ Retries – trying again 3️⃣ Idempotency – making it all a bit safe 🎥bit.ly/4lGml2meF
27
10K
Kushagar Goel
Kushagar Goel @KushagarGoel ·
If your distributed system relies on wall-clock time, it’s already wrong. Clocks drift across machines, so “last write wins” becomes luck. Systems like DynamoDB use logical/vector clocks to track causality — who caused what — not timestamps. #DistributedSystem #SoftwareArchitect
10
Kubernetes with Naveen 🇮🇳
Kubernetes with Naveen 🇮🇳 @NaveenS16 ·
If #Loki feels heavy for a small cluster, keep it boring. Use lightweight log shippers like #FluentBit or Vector to push logs straight to a managed backend or simple storage. Fewer components, less tuning, faster signal. You don’t need #distributedsystem to read yesterday’s logs.
Kubernetes with Naveen 🇮🇳 Kubernetes with Naveen 🇮🇳 @NaveenS16 ·
#Loki can feel heavy for small #Kubernetes clusters. It shines at scale, but for tiny setups memory, storage tuning, and ops overhead can outweigh benefits. If you’re spending more time babysitting logs than fixing issues, simpler log shipping might be the smarter move. #Grafana
157