Hacker News: anirudhrx

Rethinking integration testing in the age of coding agents

anirudhrx — Thu, 21 May 2026 15:36:38 +0000

Article URL: https://thenewstack.io/ci-for-coding-agents/

Comments URL: https://news.ycombinator.com/item?id=48224553

Points: 3

# Comments: 0

Fixing my writers block using OpenClaw

anirudhrx — Sun, 22 Mar 2026 18:19:23 +0000

Article URL: https://foxish.me/posts/writers-block-meet-openclaw/

Comments URL: https://news.ycombinator.com/item?id=47480457

Points: 2

# Comments: 0

Shadow Testing: a low-effort approach to solve microservices integration testing

anirudhrx — Thu, 27 Feb 2025 16:19:23 +0000

Article URL: https://thenewstack.io/microservice-integration-testing-a-pain-try-shadow-testing/

Comments URL: https://news.ycombinator.com/item?id=43195766

Points: 2

# Comments: 0

Setting up tenancy-based ephemeral environments using a service mesh

anirudhrx — Wed, 19 Feb 2025 17:51:22 +0000

Article URL: https://thenewstack.io/using-istio-or-linkerd-to-unlock-ephemeral-environments/

Comments URL: https://news.ycombinator.com/item?id=43105061

Points: 2

# Comments: 0

New comment by anirudhrx in "Show HN: Orin Marketplace: ready-to-deploy AI Agents for 50 Fintech use cases"

anirudhrx — Wed, 05 Feb 2025 18:31:34 +0000

Excited to see this! Congrats on the launch.

Rest API Testing Using Relevancy Weighted Diffs

anirudhrx — Thu, 05 Dec 2024 20:57:35 +0000

Article URL: https://www.signadot.com/blog/rest-api-testing-using-relevancy-weighted-diffs

Comments URL: https://news.ycombinator.com/item?id=42332660

Points: 1

# Comments: 0

Why Staging Doesn't Scale for Microservice Testing

anirudhrx — Fri, 16 Aug 2024 17:38:16 +0000

Article URL: https://thenewstack.io/why-staging-doesnt-scale-for-microservice-testing/

Comments URL: https://news.ycombinator.com/item?id=41268519

Points: 2

# Comments: 0

Cutting the High Cost of Testing Microservices

anirudhrx — Thu, 08 Aug 2024 15:49:05 +0000

Article URL: https://thenewstack.io/cutting-the-high-cost-of-testing-microservices/

Comments URL: https://news.ycombinator.com/item?id=41192828

Points: 6

# Comments: 0

Scaling Ephemeral Environments with OpenTelemetry and Service Mesh

anirudhrx — Wed, 18 Oct 2023 23:59:41 +0000

Article URL: https://thenewstack.io/scaling-environments-with-opentelemetry-and-service-mesh/

Comments URL: https://news.ycombinator.com/item?id=37936442

Points: 3

# Comments: 0

New comment by anirudhrx in "Goodreads is terrible for books – why can’t we all quit it?"

anirudhrx — Thu, 31 Aug 2023 16:06:32 +0000

I just use Goodreads to keep track of what I read so I can go back and see some highlights from certain kindle books that I've semi-forgotten. I dislike their goals in terms of "books/month" and "books/year" - which IMO emphasizes entirely the wrong aspect of reading and makes a meaningless quantitative assessment! Reddit for recommendations works way better.

New comment by anirudhrx in "Show HN: Langfuse – Open-source observability and analytics for LLM apps"

anirudhrx — Tue, 29 Aug 2023 23:21:14 +0000

Sorry if I'm not using the right terminology here. By layers, I'm talking about the different places from where you're emitting spans - like in your example, the UI, prompt-embedding, vector-store and context-encoding. What I was curious about was two-fold - one whether there are use-cases that make sense to have experimentation of the kind that allows a user to swap out a particular step in that stack - and second about making use of context propagation like baggage enables in OTel.

New comment by anirudhrx in "Show HN: Langfuse – Open-source observability and analytics for LLM apps"

anirudhrx — Tue, 29 Aug 2023 22:36:43 +0000

Congrats on the launch! This is really cool. Would love to see OTel integration in the future. I'm curious if this might eventually work with request-context based routing, i.e. being able to use the propagated metadata between layers to dynamically test different versions of the stack, replay requests / route to specific underlying implementation versions at different levels of the stack.

New comment by anirudhrx in "Show HN: Not My Cows – Save your cows. Blast the meteors. Giddy up"

anirudhrx — Fri, 18 Aug 2023 14:08:00 +0000

Hah! this was cool to discover.

Show HN: Developer Environments Using Istio and Kubernetes

anirudhrx — Fri, 18 Aug 2023 13:51:01 +0000

Developer environments become slow to spin up and expensive to maintain with many microservices. We’ve built a new kind of dev environment that uses traffic labeling (using OpenTelemetry) and dynamic request routing (with Istio) - which makes it lightweight and scalable.

You can run the dev version of a microservice on a laptop and connect it to a shared Kubernetes cluster with dependencies and test as though the whole application were running locally. Also, you can combine dev environments together to test different microservices with each other as they’re being developed.

The underlying approach we use is similar to Uber’s SLATE (https://www.uber.com/blog/simplifying-developer-testing-thro...) - built on top of Kubernetes and Istio.

If you’re interested, please give it a whirl using our guide at https://www.signadot.com/docs/quickstart/local-development. Looking forward to feedback, bug reports, and discussions!

Comments URL: https://news.ycombinator.com/item?id=37175595

Points: 1

# Comments: 0

New comment by anirudhrx in "Show HN: Layerform – Open-source development environments using Terraform files"

anirudhrx — Wed, 16 Aug 2023 22:52:10 +0000

This is an interesting issue that I've also seen across many companies - often even leading to low usage of these slow-to-bring-up environments. At relatively smaller scale, I can see physical infrastructure-based isolation being effective to solve it - with the stack coming up relatively quickly, but at larger scale (even 30+ microservices), I think an approach that uses logical / request tenancy is also worth considering - similar to https://www.uber.com/blog/simplifying-developer-testing-thro....

New comment by anirudhrx in "Show HN: Signadot (YC W20): Local Testing with Shared Kubernetes Clusters"

anirudhrx — Thu, 10 Aug 2023 16:51:32 +0000

Thanks for the question. Anirudh here. Firstly, there isn't always a need to isolate everything by default - in some cases, the testing being done may / application layer entities may already provide the isolation necessary.

However, there are cases like needing to test a schema change for example which can't be done at the application layer. For those cases, there's a DAG-based resource plugin (https://www.signadot.com/docs/resource-plugin-overview) framework that we built, that acts like a lifecycle hook associated with each sandbox - running containers when the sandbox is created & destroyed.

What the platform teams do to provide isolation is to write plugins that set up isolation for the sandbox as needed. The isolation is often logical tenants (as opposed to being at the infrastructure level) like a new schema / table / etc, and includes some of the data seeding / restoring a snapshot type of operations. We have some examples already of different plugins and are writing more.

New comment by anirudhrx in "Launch HN: Signadot (YC W20) – Lightweight Test Environments for Microservices"

anirudhrx — Fri, 16 Sep 2022 18:17:50 +0000

Thank you! :)

New comment by anirudhrx in "Launch HN: Signadot (YC W20) – Lightweight Test Environments for Microservices"

anirudhrx — Thu, 15 Sep 2022 21:42:16 +0000

Thanks for the kind words!

New comment by anirudhrx in "Launch HN: Signadot (YC W20) – Lightweight Test Environments for Microservices"

anirudhrx — Thu, 15 Sep 2022 19:50:21 +0000

Makes sense. I have seen a couple of instances of this pattern - with service dependencies being stitched together using configuration. Thanks for sharing!

New comment by anirudhrx in "Launch HN: Signadot (YC W20) – Lightweight Test Environments for Microservices"

anirudhrx — Thu, 15 Sep 2022 19:47:38 +0000

Ah, the primary use-case here is for developers to test microservices as changes are made to them - so one would typically be running this setup in pre-production / staging only and no prod user data would be involved. I would think of it as a way to run integration / e2e tests for each commit or pull request. Running these tests in the high fidelity test environment constructed this way reduces the bottlenecks on staging environments, and bugs are discovered / addressed sooner.