memphis VS jq

Hey check out the first good issues in the Memphis.dev open source

Try Memphis.dev blog or you can check out Github

- https://github.com/memphisdev/memphis

Argo is a collection of open-source tools for Kubernetes to run workflows, manage clusters, and do GitOps easily. Memphis is an open-source next-generation alternative to traditional message brokers.

I have dealt with the same problem. It depends what are the cycle intervals. If for example, it's every few minutes maybe it's worth keeping a machine on the cloud and the DB on that machine. in my opinion, it's a little bit expensive. The thing that worked for me is to run once a day a lambda function and store the data on a message broker. You should take a look at memphis.dev which is open-source and very easy to work with.

Image Source

Join our 2K stargazers on Github and try Memphis out, I am sure you are going to be surprised 📷 https://github.com/memphisdev/memphis-broker

That should recursively list directories, counting only the files within each, and output² jsonl that can be further mangled within the shell². You could just as easily populate an associative array for further work, or $whatever. Unlike bash, zsh has reasonable behaviour around quoting and whitespace too.

¹ https://zsh.sourceforge.io/Doc/Release/User-Contributions.ht...

² https://github.com/jpmens/jo

³ https://github.com/stedolan/jq

What I miss from jq and what is implemented but unreleased is platform independent line delimiters.

jq on Windows produces \r\n terminated lines which can be annoying when used with Cygwin / MSYS2 / WSL. The '--binary' option to not convert line delimiters is one of those pending improvements.

https://github.com/stedolan/jq/commit/0dab2b18d73e561f511801...

If you have jq installed you can use it to make the output look nicer.

It requires jq for JSON processing and GNU parallel for concurrent searches in the notebooks.

jq is your friend.

The jq command (https://stedolan.github.io/jq/) is useful pulling that information out.