# jetstream JetStream is a throughput- and memory-optimized engine for LLM inference on XLA devices, with reference implementations for JAX and PyTorch models. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## wasmCloud 2.9: NATS-native interfaces, guest memory enforcement, and Kubernetes-grade lifecycle DevFeed: [wasmCloud 2.9: NATS-native interfaces, guest memory enforcement, and Kubernetes-grade lifecycle]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-09-08T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [jetstream](), [Kubernetes](), [Messaging](), [configuration]() Tags: [configuration](), [jetstream](), [kubernetes](), [messaging](), [release](), [updates]() ### AI overview wasmCloud 2.9.0 introduces a NATS-native interface with access to Core NATS, JetStream, and key-value buckets. The release also enforces guest memory budgets in real time, adds Kubernetes-oriented lifecycle behavior, allows idle instance pools to shrink, enables guest execution metrics by default, and unifies host plugin configuration. ### Source excerpt wasmCloud 2.9 ships the NATS-native wasmcloud:nats interface with JetStream and key-value access, makes the guest memory budget enforceable, lets idle instance pools shrink, and teaches host pods to drain, probe, and survive control plane outages. ## JetStream 3: A modern benchmark for high-performance, compute-intensive Web applications DevFeed: [JetStream 3: A modern benchmark for high-performance, compute-intensive Web applications]() Original publisher: [Read original article]() Author: Chromium Blog (noreply@blogger.com) Published: 2026-03-31T18:25:00Z Content type: release Language: en Sources: [Chromium Blog]() Topics: [jetstream](), [Benchmark](), [benchmarking](), [Web](), [web applications]() Tags: [benchmark](), [benchmarking](), [browser](), [jetstream](), [none](), [the-fast-and-the-curious](), [web](), [web-applications]() ### AI overview This article introduces JetStream 3, a benchmark for high-performance, compute-intensive Web applications. It explains the benchmark's methodology, the reasons for updating JetStream 2, and the collaborative governance involving major browser-engine contributors. ### Source excerpt We're incredibly excited to announce the release of JetStream 3, built in close collaboration with Apple, Mozilla, and other partners in the web ecosystem! While we've covered the high-level details of this release in our shared announcement blog post, we wanted to take a moment here to dive a little deeper. In this post, we'll pull back the curtain on the benchmark itself, explore the methodology behind our choices, and share the motivations driving these major updates. Why Do We Benchmark, Anyway? Before we get into the "what," it helps to talk about the "why." Why do browser engineers care so much about benchmarks? At its core, benchmarking serves as a critical safety net for catching performance regressions before they ever reach users. But beyond that, benchmarks act as a powerful motivation function--a sort of "gamification" for browser engineers. Having a clear target helps us prioritize our efforts and decide exactly which optimizations deserve our focus. It also drives healthy competitiveness between different browser engines, which ultimately lifts the entire web ecosystem. Of course, the ultimate goal isn't just to make a number on a chart go up; it's to meaningfully improve user experience and real-world performance. Driven by Open Governance Just like Speedometer 3, JetStream 3 is the result of a massive collaborative effort across all major browser engines, including Apple, Mozilla, and Google. We adopted a strict consensus model for this release. This means we only added new workloads when everyone agreed they were valuable and representative. This open governance model has led to an incredibly productive collaboration with buy-in from multiple parties, ensuring the benchmark serves the best interests of the overall Web ecosystem. Ripe for an Update The last major release, JetStream 2, came out in 2019. In the technology space--and especially on the Web--six years is an eternity. There's a well-known concept in economics called Goodhart's Law, which stat ## Migrating from NATS to Redpanda: Evolve from messaging to streaming DevFeed: [Migrating from NATS to Redpanda: Evolve from messaging to streaming]() Original publisher: [Read original article]() Author: Kavya Shivashankar Published: 2025-11-18T00:00:00Z Content type: article Language: en Sources: [Redpanda]() Topics: [Messaging](), [Event-Streaming](), [jetstream](), [event driven](), [data-platforms](), [Microservice](), [Persistence](), [real-time](), [Latency](), [personalization]() Tags: [database](), [event-driven](), [event-streaming](), [jetstream](), [latency](), [messaging](), [microservices](), [persistence](), [personalization](), [pipelines](), [real-time](), [streaming]() ### AI overview This article explains how organizations can migrate from NATS and JetStream messaging to Redpanda Streaming as their systems grow from low-latency message delivery toward durable event streaming. It compares messaging and streaming requirements and presents Redpanda Connect as a way to simplify the migration. ### Source excerpt Organizations are moving from message delivery to data streaming, unlocking new capabilities, insights, and improved business value. Here's how to do the same. ## Security: Fortify 1.7.4. Released DevFeed: [Security: Fortify 1.7.4. Released]() Original publisher: [Read original article]() Author: Taylor Otwell Published: 2021-01-07T18:50:00Z Content type: release Language: en Sources: [Laravel Blog]() Topics: [Laravel](), [Security](), [Vulnerabilities](), [Pull Request](), [jetstream]() Tags: [jetstream](), [laravel](), [pull-request](), [security](), [update](), [vulnerability]() ### AI overview Laravel Fortify 1.7.4 addresses a potential security vulnerability introduced in Fortify 1.7.3. Applications using Fortify 1.7.3, including Jetstream-based applications, should be updated. ### Source excerpt We have reverted a pull request that was merged into Laravel Fortify 1.7.3 which introduced a potential security vulnerability. Please update your applications using Fortify 1.7.3, including all Jetst...