redis-protocol.rs VS hyperswitch

For what it's worth - here's a library I use in my redis client for parsing RESP2 and RESP3. It does not use serde but does use nom, and it has an optional feature that can decode `BytesMut` without moving or copying the buffer contents as long as you're willing to use the `Bytes` ecosystem types.

The latest version is a complete rewrite on async/await, tokio 1.x, the latest redis-protocol, etc. It has fundamentally different design goals compared to the popular redis-rs library and is more opinionated in its dependencies, specifically regarding tokio vs async-std, so it's probably not the right choice for certain use cases as a result. Redis-rs works well, but when we originally adopted Rust at Azuqua we had different design concerns for our Redis client and this library naturally grew in a different direction as a result.

Similarly there is https://hyperswitch.io/ open source written in Rust.

Lago is written in Ruby.

I found few others opens source billing systems written in Java.

Anyone knows anything written in nodeJS?

Read and understand the general guidelines on contributing to Hyperswitch

🚨 BTW we are hiring for several roles, apply here.

Ultimately, we believe that payments should be a basic utility like water or air. This is important because the payment ecosystem is full of closed systems and walled gardens. It is also extremely diverse (as it should be). In order to enable this diversity, payments need a trusted unifier like Linux. The road to commoditize payments will not be easy and we are looking for engineers that can make it happen. If this vision resonates with you, consider applying for Hyperswitch and we’d love to work with you! 🌟🔧🌈