Daylight reveals the extent of damage caused to Launch Complex 36 (LC-36) and the surrounding area of Cape Canaveral Space Force Station in Florida, following last night’s massive explosion of Blue Origin’s New Glenn during a Static Fire Test. Significant fire damage to the launch pad, tower, and other infrastructure can be seen - which will undoubtably require months of repairs - while debris from New Glenn lay scattered around LC-36.
Photo credit: @asherbphotos@tweetsiphotos@LaunchHeavenX
Inventory that's accurate to the second. POS that doesn't blink during peak. Mobile apps that talk to fulfillment that talks to the store.
Engineers from @Walmart, @TheHomeDepot, @Starbucks, and @AceHardware are joining us at RethinkConn 2026 to talk about how it actually gets built — at scale, across thousands of locations, in real time.
If your team runs anything connected, this is the room.
Half-day, virtual. 👉 https://t.co/TtJjljMYG7
#RethinkConn2026 #RetailTech #ConnectedRetail
NATS Server v2.14 just shipped.
(Yes, we skipped 2.13 — superstition. Don't @ us.)
A thread on what's new and why it matters if you're building on @NATS_io / JetStream 👇
Why does NVIDIA run inference on NATS?
The primitives line up exactly with what inference systems need:
pub/sub for event fan-out
request/reply for synchronous calls
JetStream for durable work queues
We're proud to share that Bruno Baloi has been recognized as an "AI Journal Thought Leader" — and his latest piece is one you'll want to read.
In "Living on the Edge: Rethinking Event-Driven Architecture for Distributed Intelligence," Bruno explores how the shift toward distributed computing is fundamentally changing the way systems must communicate, recover from failure, and make decisions in real time.
Some key takeaways:
🚀 Edge AI isn't just about speed
⛔️ In distributed environments, failure isn't the exception
📏 Event-driven systems are a natural fit for the edge, enabling resilience through asynchronous messaging and decoupled design
🐦🔥 The line between "cloud" and "edge" matters less than the ability to design systems that operate seamlessly across both.
At Synadia, this is what we think about every day — building the connective tissue for distributed, intelligent systems that work anywhere, reliably.
Read Bruno's full article here 👇
https://t.co/kHdYLYJiIX
#DistributedSystems #EdgeComputing #EventDrivenArchitecture #NATS #AI #Synadia
@jondelarroz Ur missing the worst part! In the book he risks all humanity on the chance the remote robots work after convincing himself they will not work, to save an alien race. Then he refuses to go back to see if we made it. I guess we are not worth saving?
@SirBylHolte Ur missing the worst part! In the book he risks all humanity on the chance the remote robots work after convincing himself they will not work, to save an alien race. Then he refuses to go back to see if we made it. I guess we are not worth saving?
@AdamCarollaShow@adamcarolla I had to watch it if I’m going to review it. The acting, dialogue & direction are pretty good (not Pulp Fiction good or other true Oscar worthiness). Decaprio is the anti hero. He puts in the weakest performance in the movie. Penn? Troupes & Meh!
@jondelarroz Awful story ending. He gives up on humanity. He risks the entire human race to chance to save an alien race he just met. Then when he has a chance to confirm if earth survived, he takes a pass. More self loathing - we humans suck story telling.
Pull or Push? How should you set up monitoring for your NATS systems?
How they work, when to use each, tradeoffs
Get the whole story: synadia dot com slash monitoring
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)
https://t.co/rr4VQbfAbF