Derek Collison

9.9K posts

Derek Collison banner
Derek Collison

Derek Collison

@derekcollison

CEO @synadia, creator of @nats_io and a bunch of other stuff. Past: Apcera, VMWare, Google, TIBCO, JHU/APL.

Miami FL, USA Katılım Mayıs 2007
1.5K Takip Edilen15.9K Takipçiler
Derek Collison
Derek Collison@derekcollison·
As Synadia pushes to help our customers connect data from the physical world to Intelligence, MQTT plays a critical role here. Did you know that @nats_io can natively except MQTT connections? If this sounds familiar check out the below post, worth a quick read.
Synadia@synadia

Managing fleets of edge devices with MQTT? Then you're probably shipping 𝘮𝘰𝘳𝘦 than just MQTT. Durable buffering stream replay, and command-response patterns aren't native, so teams...

English
0
3
12
873
Derek Collison retweetledi
Synadia
Synadia@synadia·
A platform bridging edge and core should support four flow control capabilities: 1. Subject/topic filtering 2. Subject mapping / traffic shaping 3. Dynamic load distribution (weighted routing) 4. Varied consumption models (push vs pull) #section-3" target="_blank" rel="nofollow noopener">synadia.com/resources/livi…
Synadia tweet media
English
0
4
10
526
Derek Collison retweetledi
Synadia
Synadia@synadia·
Our own Michael Roeschter is presenting at the Nexus SDV Release Event tomorrow in Munich alongside @googlecloud, @valtechmobility, Nexus is an open-source, AI-native platform that turns connected vehicles into continuously evolving digital products and is built to scale to millions of vehicles distributed around the globe. It's a great example of the shift happening in every industry: platforms where thousands or millions of distributed endpoints need to communicate reliably, in real time, at the edge. Doing that right requires a data backbone that natively supports everything from embedded devices to cloud superclusters. That's exactly where @nats_io and Synadia thrive — and why we're already powering SDV and autonomous mobility platforms in production today. If your applications need to run on the next-gen edge-native, fleet-scale infrastructure — whether that's vehicles, satellites or anything in between — we should talk.
Synadia tweet media
English
1
2
9
485
Derek Collison retweetledi
Synadia
Synadia@synadia·
Edge and Core as Different Realms: Separation Solves Three Recurring Edge Challenges: 1. Asynchronous Communication + Store-and-Forward 2. Different Work Belongs in Different Domains 3. Security Realms + Constrained Boundary Paths #section-2" target="_blank" rel="nofollow noopener">synadia.com/resources/livi…
English
1
2
7
441
Derek Collison retweetledi
Synadia
Synadia@synadia·
If your monitoring scrapes every 30 secs, anything that happens and resolves within that window never existed. A client connects, misbehaves, and disconnects. A connection flaps three times in ten seconds. An auth failure from an unknown source. Pull-based monitoring misses all of it
English
2
2
9
594
Derek Collison
Derek Collison@derekcollison·
Modern AI models are only as effective as the infrastructure that feeds them. In most cases, the bottleneck is not the model. It is the path between remote systems and data and the intelligence layer. To deliver measurable value, we need to modernize the connective layer first: - Secure, low-latency transport from edge to cloud - Unified event and data distribution across domains - Resiliency for intermittently connected environments - Fine-grained access control and observability AI does not fix brittle infrastructure. It amplifies it. The teams gaining traction are investing in connectivity and data movement as a first and core architectural pillar. When that layer is deliberate, secure, and real-time, AI shifts from experimentation to dependable operational value. linkedin.com/posts/synadia-…
English
0
1
2
338
Derek Collison retweetledi
Synadia
Synadia@synadia·
Every single NATS server exposes eight HTTP monitoring endpoints out of the box. (if you enable them 😉) Health status Client connections Cluster routes Leaf node links Gateway topology Subscription interest graphs JetStream resources Full server runtime state. (often called the z-endpoints)
English
1
2
6
435
Derek Collison retweetledi
Synadia
Synadia@synadia·
Is your architecture ready for edge computing? The modern edge lies at the intersection of Operational Technology (OT) and Information Technology (IT), where machines meet software sensors meet services endpoints meet intelligence
English
1
2
5
210
Derek Collison retweetledi
Tony Fadell
Tony Fadell@tfadell·
PMs don’t just ship features. They kill them. Shipping isn’t the job. Shipping the right product is. A great PM doesn’t fall in love with the roadmap. They fall in love with the problem and have the guts to say: This isn’t solving it. This adds complexity. This doesn’t matter. Every feature, setting, UI, element should fight to exist. At Nest, we had one rule: If you can’t explain why it matters, it doesn’t ship. You had to tell us the why. The reason a real person would care. That one rule killed dozens of features.
English
68
166
1.7K
279.6K
Derek Collison retweetledi
Synadia
Synadia@synadia·
We built a practical architecture guide for resilient, secure edge-to-core messaging. Learn how to build systems that thrive in disconnected, distributed environments. synadia.com/resources/livi…
Synadia tweet media
English
0
3
8
479
Derek Collison retweetledi
Synadia
Synadia@synadia·
Still building bespoke data replication pipelines? It's just not necessary with NATS JetStream. Mirror streams do it natively: one-way, automatic, and resilient to network hiccups. A few ways teams are using them: Bring data closer to users — spin up mirrors in different regions so consumers read locally instead of reaching across the world. One origin can feed multiple mirrors, so fan-out is built in. Replicate across accounts — need data flowing between different NATS accounts or domains? Mirrors handle that without custom glue code. Spread the load — flip on mirror_direct and clients read from replicas instead of hammering the origin. Your primary stream gets to breathe. Keep an independent backup — deletes on the origin don't propagate to mirrors. So your replica just... keeps everything. Nice insurance policy you didn't have to build
Synadia tweet media
English
1
2
7
591
Kelly Sommers
Kelly Sommers@kellabyte·
Blogged: Building A Distributed SQL Database in 30 days with AI A journey building HoloStore a distributed key/value store using Accord consensus protocol A surprise with HoloFusion a distributed SQL DB powered by HoloStore and Apache DataFusion Link below in the thread 🔻
Kelly Sommers tweet media
English
9
14
124
14K
Derek Collison
Derek Collison@derekcollison·
One of the many "unknown" super-powers..
Synadia@synadia

"Where did my message go?" In distributed systems, poor visibility turns small issues into long incidents—silently burning engineering time and delivery velocity. NATS solves this by making message tracing a native capability. Since 2.11, a single command reveals how a message traverses clusters, gateways, and leaf nodes—end to end. No external observability stack. No operational add-ons. No instrumentation burden on application teams. With: nats trace demo.subject "hello" operators and devs can see exactly where messages went without adding complexity to the stack. Stop chasing messages. Start shipping.

English
1
4
16
2.3K

Keşfet

@travisk @hmikitani @bchesky @nats_io @googlecloud @valtechmobility @kellabyte @elonmusk