# Messaging Published articles for Messaging. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Build a WhatsApp AI agent with Appwrite Functions and TablesDB DevFeed: [Build a WhatsApp AI agent with Appwrite Functions and TablesDB]() Original publisher: [Read original article]() Author: Atharva Deosthale Published: 2026-09-16T00:00:00Z Content type: tutorial Language: en Sources: [Appwrite Blog]() Topics: [Appwrite](), [AI Agent](), [Messaging](), [Serverless](), [API](), [Database]() Tags: [ai](), [ai-agent](), [api](), [app](), [build](), [data](), [database](), [messages](), [messaging](), [meta](), [serverless](), [support](), [tutorial](), [tutorials](), [whatsapp]() ### AI overview This tutorial shows how to build a WhatsApp AI support agent with Appwrite Functions and TablesDB. One function receives and stores incoming messages, while a second function retrieves conversation history, uses an order-lookup tool, sends replies through Meta's WhatsApp Cloud API, and stores the responses. Conversation summaries help keep long threads within the model's token budget. ### Source excerpt Turn a WhatsApp number into an AI support agent. Two Appwrite Functions receive messages and reply, TablesDB keeps the conversation history, and a compaction step keeps the context small. ## Announcing Meta Business Messaging MCP: Set up and manage WhatsApp Business from your AI agent DevFeed: [Announcing Meta Business Messaging MCP: Set up and manage WhatsApp Business from your AI agent]() Original publisher: [Read original article]() Published: 2026-09-15T14:00:49Z Content type: release Language: en Sources: [Facebook Developers]() Topics: [Model Context Protocol](), [MCP Server](), [AI Agent](), [Messaging](), [Meta](), [API]() Tags: [agent](), [ai-agent](), [api](), [mcp](), [mcp-server](), [messaging](), [meta](), [testing](), [whatsapp](), [workflow]() ### AI overview Meta announces Business Messaging MCP, an MCP server that connects AI coding agents to the WhatsApp Business Platform. It supports account and phone-number setup, message templates, webhooks, and test messages within the developer workflow. ### Source excerpt Business Messaging MCP connects your AI coding agent to the WhatsApp Business Platform, so you can create accounts, add numbers, build templates, and send test messages without leaving your workflow. ## What is CIAM in 2026 and why does it matter? DevFeed: [What is CIAM in 2026 and why does it matter?]() Original publisher: [Read original article]() Author: Ravleen Kaur Published: 2026-09-15T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [identity and access management](), [trust](), [ai-governance](), [Security](), [Artificial Intelligence](), [IAM](), [Generative AI]() Tags: [ai-agents](), [ai-governance](), [email](), [fraud](), [fraud-detection](), [identity](), [identity-and-access-management](), [industry-insights](), [messaging](), [mobile](), [trust]() ### AI overview This article explains how customer identity and access management (CIAM) is evolving from point-in-time password checks into a continuous trust and control layer. It describes CIAM's role in authenticating users, governing delegated authority for AI agents, evaluating risk across channels, and balancing low-friction access with fraud detection. It also distinguishes customer identity from workforce IAM. ### Source excerpt Discover how customer identity and access management (CIAM) uses continuous trust, deepfake defense, and agentic AI governance to protect users. ## \[Webinar\] Elevating customer engagement with WhatsApp DevFeed: [\[Webinar\] Elevating customer engagement with WhatsApp]() Original publisher: [Read original article]() Author: Twilio Published: 2026-09-11T00:00:00Z Content type: article Language: en Sources: [Twilio Blog]() Topics: [Messaging](), [Authentication](), [End-to-End Encryption](), [Encryption](), [Artificial Intelligence]() Tags: [ai](), [authentication](), [customer-engagement](), [encryption](), [enterprise](), [events-community](), [fraud](), [messaging](), [operational](), [webinar](), [whatsapp]() ### AI overview This webinar explains how businesses can use WhatsApp for secure account verification, operational alerts, two-way customer conversations, and interactive workflows. It also discusses end-to-end encryption, reducing SMS toll fraud risk, and examples of AI-powered HR messaging workflows. ### Source excerpt Stop losing critical messages in the noise. Discover how to deliver secure account verifications and operational updates via WhatsApp. ## What Is SMS Pumping Fraud and How to Stop It DevFeed: [What Is SMS Pumping Fraud and How to Stop It]() Original publisher: [Read original article]() Author: Twilio Published: 2026-09-10T00:00:00Z Content type: tutorial Language: en Sources: [Twilio Blog]() Topics: [Security](), [Messaging](), [Bot](), [Authentication](), [Forms](), [Chat Bot]() Tags: [authentication](), [automated](), [bots](), [fraud](), [how-to](), [industry-insights](), [messaging](), [otp](), [security](), [verification]() ### AI overview This article explains SMS pumping fraud, also known as SMS toll fraud, in which attackers use bots and fake phone numbers to trigger large volumes of automated SMS messages. It describes impacts such as increased messaging costs and reduced conversion rates, and introduces detection and prevention measures. ### Source excerpt SMS pumping fraud is an urgent problem for businesses that use SMS. Learn more about SMS pumping and how to prevent it. ## 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. ## Flirty OnlyFans promoters on X may be using AI to appear human DevFeed: [Flirty OnlyFans promoters on X may be using AI to appear human]() Original publisher: [Read original article]() Author: Pieter Arntz Published: 2026-09-07T11:18:00Z Content type: article Language: en Sources: [Malwarebytes]() Topics: [AI Chat](), [Script](), [Chat Bot](), [Bot](), [ASCII]() Tags: [ai](), [ascii](), [bots](), [fraud](), [generative-ai](), [messaging](), [onlyfans](), [scam](), [scams](), [scripted](), [threat-intel](), [voice]() ### AI overview An investigation examines X accounts promoting OnlyFans pages that combine repetitive flirtatious scripts with dynamic replies, raising the possibility of generative AI-assisted messaging. It warns that personalized responses and voice notes may no longer reliably distinguish people from automated accounts. ### Source excerpt Personalized replies and voice notes make it increasingly difficult to tell whether you're talking to a human, chatbot, or AI agent. ## EP224: MCP vs RAG vs AI Agents DevFeed: [EP224: MCP vs RAG vs AI Agents]() Original publisher: [Read original article]() Author: ByteByteGo Published: 2026-09-05T15:30:58Z Content type: article Language: en Sources: [ByteByteGo]() Topics: [AI Agent](), [Model Context Protocol](), [Retrieval Augmented Generation (RAG)](), [distributed-systems](), [Publish-subscribe pattern](), [Replication]() Tags: [ai-agent](), [distributed-systems](), [mcp](), [messaging](), [rag](), [replication]() ### AI overview This article compares MCP, RAG, and AI agents. It explains MCP as a standard protocol for connecting AI models to external tools and data, RAG as a way to retrieve current information from external sources, and AI agents as systems that perform tasks and make decisions autonomously. It also summarizes several distributed-systems patterns, including replication, sharding, publish-subscribe, circuit breakers, retries, and leader election. ### Source excerpt An AI agent is kind of an AI system where the agent performs the task autonomously and takes the decisions. ## wasmCloud 2.8: Async messaging, admission control, and a backstop for runaway guests DevFeed: [wasmCloud 2.8: Async messaging, admission control, and a backstop for runaway guests]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-08-26T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [Messaging](), [Resilience](), [configuration]() Tags: [async](), [interfaces](), [memory](), [messaging](), [wasmcloud]() ### AI overview wasmCloud 2.8.0 introduces asynchronous messaging interfaces with streamed payloads, typed errors, and timeouts. It also adds admission control for messaging deliveries, detects guests that consume CPU without yielding, exposes wasmtime memory tuning through Helm, and tightens related defaults. ### Source excerpt wasmCloud 2.8 ships the async wasmcloud:messaging 0.3.0 interfaces with streamed payloads, brings messaging deliveries under admission control, opens up wasmtime memory tuning, and reclaims CPU from guests that never yield. ## Chat SDK adds Instagram adapter DevFeed: [Chat SDK adds Instagram adapter]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-08-19T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [AI Bots]() Tags: [api](), [bots](), [media](), [messaging](), [meta](), [responses]() ### AI overview Chat SDK has added an Instagram adapter for building bots that handle DMs, media, quick replies, typing indicators, reactions, and story replies. It uses Meta's Instagram Messaging API and is subject to account and 24-hour reply-window requirements. ### Source excerpt You can now build bots for Instagram with the new Instagram adapter for Chat SDK. Bots can send and receive DMs and media, render cards as quick replies and link buttons, show typing indicators, receive reactions, and handle story replies. The adapter connects through Meta's Instagram Messaging API and requires a professional Business or Creator account. Messages are buffered, so streamed responses send as one message when the stream completes. Meta enforces a 24-hour messaging window, so bots can only reply within a day of the user's last message. Read the documentation to get started or browse the adapter directory. Read more ## Graceful Kubernetes Shutdowns Help Protect In-Flight Orders DevFeed: [Graceful Kubernetes Shutdowns Help Protect In-Flight Orders]() Original publisher: [Read original article]() Author: Global Technology Published: 2026-08-12T14:03:07Z Content type: tutorial Language: en Sources: [McDonald's Technical Blog - Medium]() Topics: [Kubernetes](), [distributed-systems](), [Cloud]() Tags: [cloud](), [cloud-computing](), [devops](), [distributed-systems](), [infrastructure](), [kubernetes](), [messaging](), [operations](), [scale](), [software-engineering]() ### AI overview This article explains how Kubernetes scaling, rolling updates, and cluster maintenance can interrupt in-flight requests and messages. It introduces graceful shutdown patterns in application code and infrastructure to reduce message loss and improve reliability for large-scale order processing. ### Source excerpt Why graceful shutdowns matter when millions of orders are in flight. by: Samuel Hapgood, Software Engineer III Quick Bytes At McDonald's scale, rare failures in distributed systems can impact real customer and crew experiences Graceful shutdown patterns in Kubernetes -- across application code and infrastructure -- help protect in-flight work during scaling and deployments With the right shutdown strategies, teams can reduce message loss, improve reliability, and ensure orders make it to the kitchen Imagine you're placing a mobile order at McDonald's during a busy lunch rush. You hit "submit," and the kitchen never gets the order. Now you're left waiting -- no food, no updates, and growing frustration. At first glance, it seems like an easy problem to avoid. How hard can it be to just keep track of the order? But in modern, large-scale distributed systems -- especially those that must scale continuously -- that's not always straightforward. Behind the scenes, platforms like Kubernetes (which orchestrate containerized applications in the cloud) are continuously rescheduling pods as part of normal operations such as scaling applications, performing rolling updates, and maintaining cluster health. During these transitions, in-flight requests or background messages can be interrupted in subtle ways. A pod might shut down before finishing a task, a request might be canceled mid-flight, or a message might be acknowledged by a receiving service, but never actually processed. Even with strong messaging platforms and best practices in place, application shutdowns can still interrupt in-flight work if they are not handled carefully. These are edge cases -- but at McDonald's scale, edge cases happen often enough to matter. In the US alone, our platforms support roughly one million orders per hour on a dynamically scaled cluster of hundreds of nodes. At that volume, reliability becomes critical to ensuring a seamless experience for customers, crews, and restaurant operations. Prevent ## We turned off Pub/Sub and nobody noticed DevFeed: [We turned off Pub/Sub and nobody noticed]() Original publisher: [Read original article]() Author: Patrick Hamann; Mike Fisher Published: 2026-08-11T13:56:40Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [event driven](), [Messaging](), [Publish-subscribe pattern](), [Availability](), [systems](), [Apache Pulsar](), [Cloud](), [Google]() Tags: [availability](), [broker](), [cloud](), [event-driven](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [messaging](), [outage](), [post-mortem](), [production](), [scale](), [slack](), [slack-incident]() ### AI overview This developer article explains how incident.io made its predominantly event-driven platform more resilient by adding a secondary message broker alongside Google Cloud Pub/Sub. It describes the role of message brokers and publish-subscribe processing, the risks of a single point of failure, and the successful production test in which Pub/Sub was turned off without affecting customers. ### Source excerpt Our entire event-driven platform ran through a single message broker, which made it a single point of failure. So we added a second one. This is the story of building an event load balancer, the queuing theory behind it, and the final chaos test where we turned off Pub/Sub in production and nobody noticed. ## Discord Update: August 11, 2026 Changelog DevFeed: [Discord Update: August 11, 2026 Changelog]() Original publisher: [Read original article]() Author: Clyde Published: 2026-08-11T00:00:00Z Content type: release Language: en Sources: [Discord Blog]() Topics: [changelog](), [Discord](), [App](), [Electron](), [cpu](), [Messaging](), [Security, Privacy and Abuse Prevention]() Tags: [app](), [apps](), [changelog](), [cpu](), [customization](), [data](), [discord](), [messaging](), [mobile](), [os](), [privacy](), [tools](), [update](), [updates]() ### AI overview Discord's August 11, 2026 changelog highlights new desktop formatting tools, profile privacy and customization options, friend-request notes, spoiler channels, game mentions, Meta Quest support, and ongoing settings improvements. The desktop client also upgraded to Electron 42, with incremental CPU usage improvements. ### Source excerpt Here's the Discord Changelog from August 11, 2026, so you can stay informed on what's new in recent app updates! ## I spent two months screen-sharing to ship one integration. So I rebuilt it on Temporal. DevFeed: [I spent two months screen-sharing to ship one integration. So I rebuilt it on Temporal.]() Original publisher: [Read original article]() Author: Stephen Montague Published: 2026-08-06T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [proxy](), [networking](), [legacy application](), [Messaging](), [on-prem](), [retry](), [Cloud]() Tags: [legacy-application](), [messaging](), [networking](), [on-prem](), [proxy](), [retry](), [software](), [temporal-voices]() ### AI overview The article explains how to connect a cloud application to a firewalled on-premises edge site using an egress-only proxy and a single outbound Temporal connection. It describes the operational difficulties of a legacy, one-way integration and the need for bidirectional messaging, retry handling, and testing. ### Source excerpt How to durably reach a firewalled edge site with no inbound ports: an egress-only proxy that hot-reloads config over a single outbound Temporal connection. ## Website governance for marketing: Create a framework for performance and compliance DevFeed: [Website governance for marketing: Create a framework for performance and compliance]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-07-27T00:00:00Z Content type: article Language: en Sources: [Webflow Blog]() Topics: [Web](), [Content Management System](), [Accessibility]() Tags: [article](), [best-practices](), [compliance](), [content](), [content-strategy](), [development](), [management](), [marketing](), [messaging](), [performance](), [web]() ### AI overview This article explains how web governance helps marketing teams manage growing websites consistently while maintaining content quality, performance, legal compliance, and accessibility. It introduces governance as an operating model and outlines the four Ps, including people and purpose. ### Source excerpt Learn how to structure your website governance for marketing. Explore the four Ps of governance, best practices, and common mistakes to avoid. ## Backpressure in Distributed Systems DevFeed: [Backpressure in Distributed Systems]() Original publisher: [Read original article]() Author: Pranshu Raj Published: 2026-07-23T00:00:00Z Content type: tutorial Language: en Sources: [Pranshu Raj - blog on backend systems, performance and sidequests]() Topics: [backpressure](), [distributed-systems](), [systems](), [Messaging](), [real-time]() Tags: [backpressure](), [distributed](), [distributed-systems](), [go](), [latency](), [memory](), [messages](), [messaging](), [real-time](), [systems]() ### AI overview This tutorial explains backpressure in distributed systems, including how it occurs when message producers outpace consumers and the resulting risks such as memory exhaustion, dropped messages, lower throughput, network waste, increased latency, and blocked producers. It introduces producer, messaging-system, and consumer roles and relates the topic to a real-time leaderboard project. ### Source excerpt Understanding what it is, how to deal with it, where it's used and how I handled it in the real time leaderboard. ## Why the author replaced Hermes Agent and OpenClaw with a simpler personal AI assistant DevFeed: [Why the author replaced Hermes Agent and OpenClaw with a simpler personal AI assistant]() Original publisher: [Read original article]() Author: Owain Lewis Published: 2026-07-18T10:16:21Z Content type: opinion Language: en Sources: [The AI Engineer]() Topics: [Artificial Intelligence](), [OpenClaw](), [Messaging](), [coding]() Tags: [agent](), [ai](), [coding-agents](), [messaging](), [openclaw](), [personal]() ### AI overview The author explains why Hermes Agent and OpenClaw became frustrating to use as a daily AI personal assistant, focusing on their complexity and overhyped features. The article describes the personal assistant pattern, messaging gateways, and the author's simpler solution built around organisational tasks and existing coding agents. ### Source excerpt How I built my own personal AI Chief of Staff without all the complexity. ## Chat SDK adds native Slack agent support DevFeed: [Chat SDK adds native Slack agent support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-07-17T00:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs](), [Slack](), [Bot](), [Messaging](), [Streaming](), [API]() Tags: [agents](), [ai](), [api](), [documentation](), [messaging](), [sdk](), [slack](), [streaming](), [transcripts]() ### AI overview Chat SDK now supports native Slack agents through a Slack adapter, including suggested prompts, rotating status messages, token-by-token streaming, task and plan cards, and native feedback buttons. The adapter falls back to Post+Edit where Slack streaming is unavailable and recommends Chat SDK transcripts for reconstructing AI conversation history. ### Source excerpt You can now build native Slack agents with Chat SDK's Slack adapter. The adapter supports the full Slack agent messaging experience, from agent conversations in the Messages tab to suggested prompts, rotating status messages, token-by-token streamed replies, and native feedback buttons. Here's what the adapter gives you: Suggested prompts, per thread: Pass a static payload or an async resolver that receives the thread context, including what the user is currently viewing under agent_view. Prompts are pinned automatically whenever an agent thread opens. Native streaming with a fallback: Streamed replies render token-by-token via Slack's streaming API, including task and plan cards. If a workspace doesn't support streaming (e.g., GovSlack), the adapter switches to Post+Edit. Built-in feedback: Set feedbackButtons: true to append thumbs-up/down buttons to every streamed reply, and clicks dispatch via the bot.onAction flow. One thing to know: under agent_view, Slack threads each user message individually, so channel history only returns the user's side of a DM. Use Chat SDK transcripts to build AI conversation history instead. Read the documentation to get started, or begin with one of our templates. Read more ## Amazon SQS turns 20: Two decades of reliable messaging at scale DevFeed: [Amazon SQS turns 20: Two decades of reliable messaging at scale]() Original publisher: [Read original article]() Author: Esra Kayabali Published: 2026-07-13T18:13:57Z Content type: article Language: en Sources: [AWS News Blog]() Topics: [Amazon Simple Queue Service (SQS)](), [distributed-systems](), [Amazon Web Services](), [Encryption](), [Security](), [Availability]() Tags: [amazon](), [amazon-simple-queue-service-sqs](), [amazon-sqs](), [announcements](), [availability](), [distributed-systems](), [encryption](), [launch](), [messaging](), [news](), [performance](), [scale](), [security](), [systems](), [transactions]() ### AI overview Amazon SQS marks its 20th anniversary with a retrospective on reliable, asynchronous messaging and the decoupling of producers from consumers. The article highlights recent developments including higher-throughput FIFO queues, default server-side encryption, and dead-letter queue redrive enhancements. ### Source excerpt On July 13, 2006, we launched Amazon Simple Queue Service (Amazon SQS) as one of the first three services available to customers, alongside Amazon EC2 and Amazon S3. We had learned firsthand that distributed systems need a reliable way to pass messages between components without creating tight dependencies. If one service called another directly and [...] ## Kafka vs RabbitMQ vs SQS DevFeed: [Kafka vs RabbitMQ vs SQS]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-07-02T03:31:11Z Content type: comparison Language: en Sources: [AlgoMaster Newsletter]() Topics: [Amazon Simple Queue Service (SQS)](), [Kafka](), [RabbitMQ](), [Messaging](), [Back end]() Tags: [backend](), [kafka](), [messaging](), [queues](), [rabbitmq](), [sqs]() ### AI overview This comparison examines Kafka, RabbitMQ, and Amazon SQS for asynchronous systems. It explains that Kafka uses an append-only log with consumer offsets and replay, RabbitMQ routes messages through exchanges and queues with acknowledgments, and SQS provides managed queue-based messaging that consumers poll. ### Source excerpt Most backend systems eventually need one service to hand off work to another asynchronously. ## Gamaredon in 2025: Leveraging tunnels, workers, dead drops, and new alliances DevFeed: [Gamaredon in 2025: Leveraging tunnels, workers, dead drops, and new alliances]() Original publisher: [Read original article]() Author: Zoltán Rusnák Published: 2026-06-25T08:45:00Z Content type: article Language: en Sources: [WeLiveSecurity]() Topics: [Security Attacks]() Tags: [apt](), [cloud](), [dns](), [eset-research](), [infrastructure](), [messaging](), [powershell](), [social-media](), [storage]() ### AI overview ESET Research analyzes Gamaredon's 2025 cyberespionage activity against Ukrainian governmental and military institutions, including spearphishing, new malicious PowerShell tools, cloud-based data exfiltration, and concealed C&C infrastructure. ### Source excerpt ESET Research analyzes Gamaredon's new toolset and the group's growing reliance on legitimate online services to hide its C&C infrastructure and exfiltrate stolen data ## Chat SDK adds Sendblue support DevFeed: [Chat SDK adds Sendblue support]() Original publisher: [Read original article]() Author: Ben Sabic Published: 2026-06-22T14:00:00Z Content type: release Language: en Sources: [Vercel News]() Topics: [SDKs]() Tags: [bots](), [messaging](), [support]() ### AI overview Chat SDK adds an official Sendblue adapter for bots that exchange iMessage, SMS, and RCS messages. It maps Sendblue conversations and inbound messages to Chat SDK threads and messages. ### Source excerpt Chat SDK now supports Sendblue with the new vendor-official adapter. Build bots that send and receive iMessage, SMS, and RCS through Sendblue's hosted gateway, reaching people on the messaging apps they already use. Messages use iMessage-first delivery with support for automatic SMS and RCS fallback, tapbacks, typing indicators, and delivery status callbacks. The adapter maps each Sendblue conversation to a Chat SDK thread, tied to a specific phone line and contact (or group), and each inbound iMessage, SMS, or RCS message to a Chat SDK message. Read the Sendblue documentation to get started. Read more ## GCP Pub/Sub connector for ClickPipes is now in Private Preview DevFeed: [GCP Pub/Sub connector for ClickPipes is now in Private Preview]() Original publisher: [Read original article]() Author: Marta Paes Published: 2026-06-17T20:53:04Z Content type: release Language: en Sources: [ClickHouse Blog]() Topics: [clickhouse](), [Messaging](), [real-time](), [Cloud](), [data](), [Monitoring](), [JSON](), [OpenAPI Specification](), [Terraform]() Tags: [analytics](), [clickhouse](), [cloud](), [data](), [event](), [events](), [gcp](), [infrastructure](), [json](), [logs](), [messaging](), [metrics](), [monitoring](), [openapi](), [real-time](), [terraform](), [tooling]() ### AI overview ClickHouse announces a private-preview GCP Pub/Sub connector for ClickPipes, enabling real-time streaming into ClickHouse Cloud without routing through GCS or Dataflow. The connector supports JSON, Avro, Protobuf, schema registry integration, message filtering, seek options, ordered delivery, scaling, retries, metrics, monitoring, and detailed logs. ### Source excerpt Stream data from Pub/Sub in a few clicks for blazing-fast analytics over GCP infrastructure logs, application events, and operational signals. No routing through GCS or Dataflow required. ## wasmCloud 2.4.0: HPA + KEDA autoscaling, multi-handler workloads, pluggable NATS DevFeed: [wasmCloud 2.4.0: HPA + KEDA autoscaling, multi-handler workloads, pluggable NATS]() Original publisher: [Read original article]() Author: Eric Gregory Published: 2026-06-17T00:00:00Z Content type: release Language: en Sources: [wasmCloud Blog]() Topics: [wasm](), [Kubernetes](), [autoscaling](), [Messaging](), [Security]() Tags: [autoscaling](), [handler](), [helm](), [kubernetes](), [messaging](), [net-11-preview-7](), [opentelemetry](), [prometheus](), [security](), [wasmcloud]() ### AI overview wasmCloud 2.4.0 adds Kubernetes-native autoscaling for Wasm workloads through HPA and KEDA, multi-handler messaging workflows, expanded Helm configuration, a redesigned host plugin API, and a Wasmtime 45.0.2 security update. ### Source excerpt wasmCloud 2.4.0 brings Kubernetes-native autoscaling for Wasm workloads via HPA and KEDA, multi-handler messaging in wash dev, a Helm chart NATS overhaul with split scheduler/data URLs, a NATS-backed operator liveness probe, and a Wasmtime 45.0.2 security bump. [Next page]()