NATS VS memphis

[1] https://github.com/nats-io/nats-server/issues/6832#issuecomm...

https://nats.io is easier to use than Kafka and already solves several of the points in this post I believe, like removing partitions, supporting key-based streams, and having flexible topic hierarchies.

Look at the contribution history, basically all active contributors work for Synadia: https://github.com/nats-io/nats-server/graphs/contributors

That's not a healthy / functioning open source community. Less than 30 people have made more than 10 commits; most of the 160 were "drive by" who fixed a single small thing.

NATS, with its lightweight and high-performance design, offers features well-suited for sandbox testing. We can leverage NATS queue groups, which function similarly to Kafka consumer groups.

In today’s dynamic cloud environments, managing Kubernetes resources across multiple clusters can be a complex task. Traditional methods often lack the agility and event-driven architecture needed to respond quickly to changes and automate resource provisioning. This article explores how Sveltos, in conjunction with NATS and JetStream, simplifies multi-cluster Kubernetes management through event-driven automation, streamlining operations and improving responsiveness.

hey thanks!

definitely interesting!

I do wonder if this really solves the author problem because by the looks of it , you just have to run meta command and it would run over each of the sub directory. While at the same time , I think I like it because this is what I think people refer to as "modular monolith"

Combining this with nats https://nats.io/ (hey if you don't want it to be over the network , you could use nats with the memory model of your application itself to reduce any overhead) and essentially just get yourself a really modular monolith in which you can then seperate things selectively (ahem , microservices) afterwards rather easily.

and now decided to write more complex things using https://nats.io and https://data-star.dev -

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