Company blog of MetalBear, makers of mirrord, on Rust, hooking libc calls, Kubernetes operators and cloud development workflows.
HN links it mainly for mirrord's internals, such as hooking libc functions in Rust, and for explaining how it speeds up development against remote Kubernetes environments.
So there are a bunch of use cases, but the main one we think is during day to day development. mirrord can give you access to “cloud conditions” while you code, without having to go through CI and actually deploying, which a. makes your feedback loops a lot tighter and b. reduces the likelihood you’ll deploy something broken to the cloud (i.e. staging/production) environment and break it for other developers in the organization.
We wrote about it a bit more here if you’re interested: https://metalbear.co/blog/reintroducing-mirrord/
mirrord is a tool for backend engineers that enables them to work on a remote environment without needing to deploy there or actually run there.
It makes the iteration time (code -> test -> [review] -> deploy) faster since you don't replace the remote service also, which means many devs can work the same time.
You can read more about it here https://metalbear.co/blog/mirrord-3.0-is-out/
Hey, seems like node uses libuv and in fact we did a blogpost on it!
https://metalbear.co/blog/mirrord-internals-hooking-libc-functions-in-rust-and-fixing-bugs/
There is also https://metalbear.co/blog/writing-a-kubernetes-operator/