bruth

5 ms·

1.
by bruth 11mo ago
Unfortunately the LLM is leading you astray :)
2.
by bruth 11mo ago
(disclaimer: I am the VP of Prod/Eng at Synadia) NATS - An application connectivity technology (L7). It was originally designed for low-latency M:N messaging, and that is still true today. In 2018, native multi-tenancy, clustering opti
3.
by bruth 2y ago
I don't know Simon personally, I do know he has been blogging for a very long time and many of his posts are for his own benefit of recall, not necessarily intended for an external audience. Also He did not post this, a different perso
4.
by bruth 3y ago
(Disclaimer: I am a NATS maintainer and work for Synadia) The parent comment may have been referring to the fact that NATS has support for durable (and replicated) work queue streams, so those could be used directly for queuing tasks and ha
5.
by bruth 3y ago
If a learning resource is lacking or confusing, Slack or GitHub issues/discussions is a way to engage and provide feedback so they can be improved. If the docs were confusing, there are other channels to get help to unblock folks. The
6.
by bruth 3y ago
> You're in your own little bubble and expect people to be mind readers. Out of curiosity, have you asked questions in Slack or Github? If so, and you had a bad experience with the interaction, I get the sentiment and would offer he
7.
by bruth 3y ago
This post is about a product for NATS. I presume you are talking about the roadmap after the 2.10 release?
8.
by bruth 3y ago
Yes that reads correct. The `sub` would a NATS user public nkey, the `iss` would be the NATS account public nkey (either the issuer nkey in config-mode or existing nkey in decentralized auth). As long as it can verify the chain of trust for
9.
by bruth 3y ago
Auth callout is post-NATS client authentication, so it would not solve the "auth web flow" for authentication. Instead, the resulting token from that would be set as a cookie that then would be passed into the nats.ws client conne
10.
by bruth 3y ago
> Seems like I need to write a service utilizing NATS which talks to the OIDC server. Auth callout was designed to be a generic extension point to delegate authentication and generate dynamic a user JWT that NATS understands (permissions
11.
by bruth 4y ago
> If messages were frequent enough, and/or snapshots took a while to compute/transfer, you might never have a roll-up succeed. Yes, good point. The "snapshotting up to a lagging sequence" could be achieved with two se
12.
by bruth 4y ago
#1: Correct, I putting together an example this week to show what this looks like. Pretty straightforward. #2: You can combine rollup and expected last sequence header to prevent this, unless I am missing another subtle detail? (I am enjoyi
13.
by bruth 4y ago
#1: This isn't a hard requirement to achieve the desired permissions. For the DriftDB use case, my understanding is that all members in the room have full pub/sub k/v permissions, so that could be achieved by declaring a new
14.
by bruth 4y ago
It is a top priority. I do appreciate the constructive criticism and conversation. Feel free to reach out to me (byron at synadia dot com) or on the NATS Slack ( https://slack.nats.io ).
15.
by bruth 4y ago
> Would appreciate it if you disclosed your affiliation with Synadia and NATS before advertising it. Fair point, but I did not mention Synadia. FWIW, I have been a NATS user for seven+ years prior to joining Synadia so I was speaking on
16.
by bruth 4y ago
> Even with NATS jetstream, NATS has a focus on service communication. It indeed excels at service communication as well. However, a core use case for NATS is the edge, be it your definition (browsers and mobile), but also in cars, facto
17.
by bruth 4y ago
Was not aware of Plane, nice! Regarding the two points: - A unique room ID/subject is a form of authentication. Essentially anyone having that unique identifier can join, akin to a token. This is straightforward to setup in NATS avoidi
18.
by bruth 4y ago
In fact it does all of these things now properly! STAN (NATS Streaming) was deprecated two years ago in favor of a new embedded subsystem called JetStream: https://docs.nats.io/nats-concepts/jetstream released in March
19.
by bruth 4y ago
Nice, have you come across NATS? https://nats.io . The server natively supports WebSockets. There are many clients including Deno, Node, WebSockets, Rust, Go, C, Python, etc. In addition to stateless messaging, it supports durabl
20.
by bruth 4y ago
Check out SimpleIoT: https://github.com/simpleiot/simpleiot
21.
by bruth 4y ago
If you have a low-volume, non-performant, non-critical database, k8s is fine. If you need it to perform and/or need built-in ops (managed backups or replication), use a managed service. k8s _can_ do stateful, but if a managed service e
22.
by bruth 5y ago
Changelog podcast with the author: https://changelog.com/podcast/482
23.
Functional Event Sourcing Decider(thinkbeforecoding.com)
2 points by bruth 5y ago|0 comments
24.
by bruth 5y ago
You may be thinking of NATS Streaming which was a predecessor to JetStream. It was indeed a standalone thing that used NATS under the hood. JetStream is now baked into the NATS server.
25.
by bruth 5y ago
The Children's Hospital of Philadelphia | Bioinformatics Scientist | Philadelphia, PA | Full-time | Remote or Onsite This role will work with bioinformatics scientists and software engineers to operationalize a set of pipelines used to
26.
by bruth 5y ago
They aren't solving the same problem. An event sourced entity (should) have a very small scope. It acts as a consistency boundary around some bit of state. Each event in "the stream" for that entity represents a state change.
27.
by bruth 5y ago
I have not watched that clip, but as I said above, Confluent isn't a good resource for defining this term since Kafka cannot be used to do ES. I would suggest an article like: https://domaincentric.net/blog/eventst
28.
by bruth 5y ago
The title here is being overlooked, its not _terrible_, its _hard_. Also this quote from the article: > The bulk of these probably fall under "he obviously didn't understand X," or "you should never do Y!" in whi
29.
by bruth 5y ago
I appreciate the response! My first thought and assumption was indeed there are backend costs given the size limitations you mentioned. But I suppose if that is sufficient for some folks, then they can benefit from that without requiring a
30.
by bruth 5y ago
Why is it 3.99 for a lifetime payment? My cynical self tells me the product won't improve or your intention is generate enough hype to make a quick exit and the product will go away. You should make this is a recurring cost.

More ›