Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

High-Performance server for NATS.io, the cloud and edge native messaging system

github.com

Post reply on HN
Print view View original

71–75 of 75 posts

Re: High-Performance server for NATS.io, the cloud and edge native messaging system

#71

Post by xuancanh »

re-thc wrote: post #33
xuancanh wrote: post #32

Earlier quoted context omitted.

That is not what cloud native means. It is an overloaded term, but the basic idea is that the application is designed to operate in the cloud environment, utilizing cloud's capabilities such as elastic and automated infrastructure management.

> That is not what cloud native means. > utilizing cloud's capabilities such as elastic and automated infrastructure management. Contradictory perhaps? So it's not what it means but it is what it means? In order to achieve what you've said in vague terms you definitely do need to try to be stateless, have fast startup and reduce memory. Clear examples are things like lambda and fargate. How can you be elastic if you…

I'm pretty sure that Aurora DB can be called a "Cloud-native application" but its startup time is not fast and memory footprint is not small.

Re: High-Performance server for NATS.io, the cloud and edge native messaging system

#72

Post by gedw99 »

rcombatwombat wrote: post #66
Kinrany wrote: post #58

Earlier quoted context omitted.

Jetstream is distributed as an optional part of NATS, so while it exists as a layer on top of NATS Core and provides a different model, describing NATS as entirely stateless is not totally accurate Though I suspect that Synadia people might do at least one more minor iteration of Jetstream: it still seems a little more complex than it needs to be, unlike Core

See https://github.com/nats-io/nats.go/tree/main/jetstream#readm...

what do you think of the new JetStream API ?

Re: High-Performance server for NATS.io, the cloud and edge native messaging system

#73

Post by gedw99 »

throw14082020 wrote: post #40
throw14082020 wrote: post #39

Would it ever make sense for NATS to support UDP or SRTP?

Ahh, they may work on QUIC this year: https://github.com/nats-io/nats-server/issues/457

i think they are waiting for QUIC to be merged into golang

Re: High-Performance server for NATS.io, the cloud and edge native messaging system

#74

Post by gedw99 »

rcombatwombat wrote: post #69
lakomen wrote: post #57

Earlier quoted context omitted.

This is actually a good idea, I'll try that, thanks :) But, you know, it's still a bit more complicated than opening the browser's debug console and inspecting request and response in the networking tab. Yeah you have operators, which are essentially the auth admins or orgs, however you'd like to look at it, then there are accounts which are an alias for "project name" and then you have users, which are "client name"…

The 'auth callout' feature introduced in NATS 2.10 is there exactly for that (integrating NATS auth with whatever existing IdP system you already have): the client app passes whatever you use as it's credentials at connection time the server then passes them to the security callout service (something you write, following a template that receives whatever the client app passed as credentials and then works with whatev…

this is exactly what i need.

thanks.

Wondering if there any examples of this ?

Re: High-Performance server for NATS.io, the cloud and edge native messaging system

#75

Post by gedw99 »

SebastianM wrote: post #51
lakomen wrote: post #21

I got into it again about 2 weeks ago. Been doing a small project with the microservice api. Compared to HTTP/REST I miss the debugabilty of it. Since all messages are sent over websocket and received, in binary form, since there is no support from Chrome or Firefox, one has to tediously manually extract the json payload and try to make sense of it. Jetstream is still quite the mystery. It just doesn't want to work t…

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/

this sounds really awesome.
Post reply on HN