Inter-System Messaging with NATS & Jetstream (with Jeremy Saenz)
Vložit
- čas přidán 16. 07. 2024
- Most message systems have an opinion on the right way to do inter-systems communication. Whether it’s actors, queues, message logs or just plain ol’ request response, nearly every tool has decided on The Right Way to do messaging, and it optimises heavily for that specific approach. But NATS is absolutely running against that trend.
In this week’s episode, Jeremey Saenz joins us to talk about NATS, the Cloud Native Computing Foundation’s configurable message-passing and data-transfer system. The promise is a tool that can happily behave like a queue for one channel, a log like another and a request/response protocol for the third, all with a few client flags.
But how does that work? What’s it doing under the hood, what features does it offer, and what do we lose in return for that flexibility? Jeremy has all the answers as we ask, what is NATS really?
-
NATS on Github: github.com/nats-io/nats-server
NATS Homepage: nats.io/
Getting Started with NATS: • The coolest OSS projec...
Developer Voices Episode on Benthos: • Shouldn't Data Connect...
CNCF: www.cncf.io/
The Ballerina Language: ballerina.io/
Kris on Mastodon: mastodon.social/@krisajenkins
Kris on LinkedIn: / krisjenkins
Kris on Twitter: / krisajenkins
Support Developer Voices via Patreon: / developervoices
Support Developer Voices via CZcams: / @developervoices
--
0:00 Intro
3:12 Podcast
1:09:22 Outro
excellent show, as always!
Congrats to monetizing! Well earned, I'm grateful for the transparency and brevity. Very, very classy method, as const 😘 model CZcamsr, that's how it's done.
There goes my weekend…
One of my favorite tools. The payload agnosticism and default nearest delivery are my two favorite aspects
Didn't expect this for sure.
I watch Jeremy's casts for longer than yours.
Interesting topic! Supr as always. Happy to support you on Patreon!
Chris can you open up a ko-fi account so I don't have to send money to patreon corp?
10mins in ... He still hasnt even tried to answer the basic question.
Help !!
Swiss army penknife ?
what happens when nats hard down. Whole solution build on it is down too? Some apps just cannot get whole hard down, your SLA will not allow it. so you need to build solution without shared resources like nats and rather building silos. Then you need to diverge to that http stuff, webhooks, grpc. To the other hand I see NATS ok inside silo.
You can build clusters and streams can have replicas so if you have many nodes your applications will switch to other member of the cluster.
This guy can’t answer any questions properly.
horrible vid, I watched the whole thing and still have no idea how NATS works