NATS: you need it now! ↦
If you are running Kubernetes, or really any kind of microservice architecture, you will eventually run into challenges with communication and synchronization between your instances. To solve this, I recommend deploying an instance of NATS as part of your initial infrastructure setup.
NATS is great! I tell you why in this blog post.
Sign in or Join to comment or subscribe
Mt Holly, NC
More people should investigate NATS. There are so many things that you can remove from your infrastructure by using it. Derek Collison (CEO of Synadia, creator or NATS), recently posted this list of what you no longer need:
Take a look here: https://nats.io
Jerod co-hosts The Changelog, crashes JS Party, and takes out the trash (his old code) once in awhile.
That’s a compelling list of things to not need!
That’s a really interesting list of things to deprecate with NATS. I can see how most of them can become unnecessary, but not all of them. Can you point me for example to an explanation of how NATS makes K8s irrelevant?
Mt Holly, NC
Derek gave a clarification o the K8S item 😎:
“Please note you can of course deploy a NATS application in K8/3S, but its not required was my point to get a global microservices mesh working.”
I still think K8S is relevant for deploying applications…depending on the situation of course.
Ah, got it. You’re saying NATS can be used without Kubernetes. I thought you were saying “NATS can replace Kubernetes”, and that’s what got me confused :-D