LogDevice vs Zap: What are the differences?

Developers describe LogDevice as "Log storage for high-durability low-latency streaming use cases (by Facebook)". LogDevice is a scalable and fault tolerant distributed log system. While a file-system stores and serves data organized as files, a log system stores and delivers data organized as logs. The log can be viewed as a record-oriented, append-only, and trimmable file. On the other hand, Zap is detailed as "Blazing fast, structured, leveled logging in Go (by Uber)". Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API.

LogDevice and Zap can be categorized as "Logging" tools.

LogDevice and Zap are both open source tools. Zap with 7.22K GitHub stars and 553 forks on GitHub appears to be more popular than LogDevice with 1.52K GitHub stars and 136 GitHub forks.