arcadia VS natscli

I saw your cobra i18n project on GitHub at https://github.com/snivilised/arcadia

I have created a cli helper Go library, Cobrass designed to complement Cobra. I am also creating a template repo Arcadia designed to speed up the process of creating a cobra cli with i18n support.

Nats provides a nice CLI that can help with debugging: https://github.com/nats-io/natscli

Besides that I'm also working on a UI solution, that will help to get better overview of your cluster: https://qaze.app/

You should just use the `nats` CLI tool (https://github.com/nats-io/natscli/) instead.

This cli is used by NATS cli which itself needs to use json schema to drive it and so shows the concept of using data to drive itself at https://github.com/nats-io/natscli

In this article, we’ll take a look at NATS CLI and learn some basics commands. In my opinion NATS CLI is quite underrated, it offers many features and can help eliminate most of the manual scripts used to manage a NATS server.

Now let’s use the NATS CLI and do a simple benchmark to generate some publish/subscribe events.

Next, we will need the NATS CLI. We can simply install it for Linux from the GitHub releases page.

NATS CLI

While running nats server using cli or docker container is usually the preferred way but in some instances, it can be unnecessary, one such example is testing. While testing, it’s often cumbersome to spin up new instances for external services, this can be completely avoided by using an in-memory server. Luckily, NATS server package provides this functionality out of the box!