Threads for eyal

    1. 2

      There must be a huge latency penalty with this setup, which would preclude some uses. But I’m wondering if you could use VS Code remote on a VM next to the k8s cluster and get almost the same dev experience without having the app see extra latency.

      1. 3

        Hey, one of mirrord’s maintainers here. There’s of course extra latency as traffic has to go from your machine to the cluster and back, but as the common use case for mirrord isn’t performance-intensive to begin with (testing functionality of new code, or debugging existing issues in the cloud), this isn’t really a factor for most of its users.

        But as you suggested, it is possible to use mirrord in tandem with a development machine within the cluster. We’re seeing this happen in organizations that already use a remote development environment solution like Gitpod.

        1. 3

          Testing new code or debugging in a performance-intensive service is performance-intensive, right? Like, if I’m working on an authz service or database proxy and everything else expects it to respond in a millisecond, it’s going to be a problem. So it’s good there’s a way to get this experience (which sounds great) in that situation.

    2. 3

      Certify yourself with official courses.

      Is this a common opinion? Curious to hear about certifications devs took and didn’t later think their time would’ve been better spent otherwise.

    3. 2

      Wondering how mirrord differs from https://www.telepresence.io? Can anyone shed light?

      1. 3

        If you read the article until the end, you will find an answer.

      2. 1

        Hey, in addition to the differences listed in the article (centered on concurrent usage of the shared environment), there are the differences listed here: https://mirrord.dev/docs/overview/faq/#how-is-mirrord-different-from-telepresence

        tl;dr:

        • Supports traffic mirroring
        • You don’t have to install anything on your k8s cluster
        • Works at the process level rather than at the network level, providing for an easier setup and a smoother UX