# Messaging

Messaging is a software architecture mechanism in which applications exchange data through channels such as queues, topics, and event buses, often asynchronously.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Reduce the complexity and cost of real-time processing with queues in Amazon Kinesis Data Streams

DevFeed: [Reduce the complexity and cost of real-time processing with queues in Amazon Kinesis Data Streams](<https://devfeed.tech/articles/reduce-the-complexity-and-cost-of-real-time-processing-with-queues-in-amazon-kinesis-data-streams-140167.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/big-data/reduce-the-complexity-and-cost-of-real-time-processing-with-queues-in-amazon-kinesis-data-streams/>)

Author: Dirk Fröhner

Published: 2026-11-17T23:17:16Z

Content type: article

Language: en

Sources: [AWS Big Data Blog](<https://devfeed.tech/sources/aws-big-data-blog.md>)

Topics: [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [stream-processing](<https://devfeed.tech/topics/stream-processing.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>), [Amazon S3](<https://devfeed.tech/topics/amazon-s3.md>)

Tags: [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-kinesis](<https://devfeed.tech/tags/amazon-kinesis.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [backlog](<https://devfeed.tech/tags/backlog.md>), [complexity](<https://devfeed.tech/tags/complexity.md>), [cost](<https://devfeed.tech/tags/cost.md>), [data](<https://devfeed.tech/tags/data.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [demand](<https://devfeed.tech/tags/demand.md>), [instead](<https://devfeed.tech/tags/instead.md>), [kinesis](<https://devfeed.tech/tags/kinesis.md>), [kinesis-data-streams](<https://devfeed.tech/tags/kinesis-data-streams.md>), [offers](<https://devfeed.tech/tags/offers.md>), [one](<https://devfeed.tech/tags/one.md>), [processing](<https://devfeed.tech/tags/processing.md>), [queues](<https://devfeed.tech/tags/queues.md>), [real-time](<https://devfeed.tech/tags/real-time.md>), [reduce](<https://devfeed.tech/tags/reduce.md>), [streams](<https://devfeed.tech/tags/streams.md>), [time](<https://devfeed.tech/tags/time.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Amazon Kinesis Data Streams queues provide per-record delivery tracking for applications that can process records independently. Consumers receive batches of up to 10 records, process them, and acknowledge them; unacknowledged records become available again after a configurable visibility timeout. Delivery is at least once and ordering is best effort, so processing should be idempotent. Records that exceed the default six receives without acknowledgment go to a dead-letter state, where operators can inspect, restore, or discard them. Queues scale consumer instances with backlog rather than shard count and remove the need for a KCL lease table and per-shard custom metrics. Multiple queues, stream consumers, and managed delivery can use the same stream without a relay or duplicate ingest. Use direct stream consumers when processing depends on record order or prior state; use queues for independent work. AWS reports up to 43% lower processing cost, but its synthetic benchmark used an I/O-bound handler; savings depend on workload and configuration, and CPU-bound work narrows the compute benefit.

### Source excerpt

Amazon Kinesis Data Streams now offers queues, a new way to consume the records of an on-demand stream. A queue delivers records one by one, tracks each record's delivery state, redelivers unacknowledged records, sets persistently failing records aside as dead letters, and scales with your backlog instead of your shard count.

## Agent fleets drag the messaging layer from afterthought to AI's coordination core

DevFeed: [Agent fleets drag the messaging layer from afterthought to AI's coordination core](<https://devfeed.tech/articles/agent-fleets-drag-the-messaging-layer-from-afterthought-to-ai-s-coordination-core-132510.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/13/data-center-telemetry-runs-nats-graduates-from-cncf-kubeconna/>)

Author: Ryan Stevens

Published: 2026-11-13T17:23:02Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [middleware](<https://devfeed.tech/topics/middleware.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [agent-fleets](<https://devfeed.tech/tags/agent-fleets.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-systems](<https://devfeed.tech/tags/agentic-systems.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-factory](<https://devfeed.tech/tags/ai-factory.md>), [ai-inference](<https://devfeed.tech/tags/ai-inference.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [andrew-connolly](<https://devfeed.tech/tags/andrew-connolly.md>), [cloud-native](<https://devfeed.tech/tags/cloud-native.md>), [cloud-native-computing-foundation](<https://devfeed.tech/tags/cloud-native-computing-foundation.md>), [cloud-security](<https://devfeed.tech/tags/cloud-security.md>), [cloudnativecon](<https://devfeed.tech/tags/cloudnativecon.md>), [cncf](<https://devfeed.tech/tags/cncf.md>), [cube-event-coverage](<https://devfeed.tech/tags/cube-event-coverage.md>), [data-center](<https://devfeed.tech/tags/data-center.md>), [developer-platforms](<https://devfeed.tech/tags/developer-platforms.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [gpu-infrastructure](<https://devfeed.tech/tags/gpu-infrastructure.md>), [infra](<https://devfeed.tech/tags/infra.md>), [john-furrier](<https://devfeed.tech/tags/john-furrier.md>), [kubecon](<https://devfeed.tech/tags/kubecon.md>), [kubecon-plus-cloudnativecon-na-2026](<https://devfeed.tech/tags/kubecon-plus-cloudnativecon-na-2026.md>), [kubeconna](<https://devfeed.tech/tags/kubeconna.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [news](<https://devfeed.tech/tags/news.md>), [observability](<https://devfeed.tech/tags/observability.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [platform-engineering](<https://devfeed.tech/tags/platform-engineering.md>), [rebecca-knight](<https://devfeed.tech/tags/rebecca-knight.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [thecube](<https://devfeed.tech/tags/thecube.md>), [waldemar-quevedo](<https://devfeed.tech/tags/waldemar-quevedo.md>)

### AI overview

NATS is being used to coordinate machine-to-machine traffic as short-lived AI workloads and agent fleets increase connection churn. Its topic-based messaging and super-cluster gateways route traffic across data centers, regions, availability zones and clouds. The article also cites uses for power and cooling telemetry and Nvidia's AI factory event bus. JetStream persistence and the key-value store can preserve state for agent handoffs. These examples and capabilities are attributed to NATS maintainers; the excerpt does not provide performance comparisons or independent evaluation.

### Source excerpt

Data center telemetry, sandboxed AI workloads and fleets of agents are pushing more machine-to-machine traffic through infrastructure than ever before, exposing the limits of messaging systems built for steadier demand. That shift is drawing attention to the Neural Autonomic Transport System, an open-source messaging system that lets applications and services exchange messages by topic. Created [...] The post Agent fleets drag the messaging layer from afterthought to AI's coordination core appeared first on SiliconANGLE.

## Transitioning Your Communications: How to Keep Customer Messages Flowing Seamlessly

DevFeed: [Transitioning Your Communications: How to Keep Customer Messages Flowing Seamlessly](<https://devfeed.tech/articles/transitioning-your-communications-how-to-keep-customer-messages-flowing-seamlessly-129462.md>)

Original publisher: [Read original article](<https://www.twilio.com/en-us/blog/partners/integrations/transition-communications-tyntec-twilio>)

Author: Henry Guyver

Published: 2026-11-11T00:00:00Z

Content type: article

Language: en

Sources: [Twilio](<https://devfeed.tech/sources/twilio-blog.md>), [Twilio Blog](<https://devfeed.tech/sources/twilio-blog-2.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [Iterable](<https://devfeed.tech/topics/iterable.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [communications](<https://devfeed.tech/tags/communications.md>), [customer](<https://devfeed.tech/tags/customer.md>), [data](<https://devfeed.tech/tags/data.md>), [data-privacy](<https://devfeed.tech/tags/data-privacy.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [keep](<https://devfeed.tech/tags/keep.md>), [learn](<https://devfeed.tech/tags/learn.md>), [messages](<https://devfeed.tech/tags/messages.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [more](<https://devfeed.tech/tags/more.md>), [partners-ecosystems](<https://devfeed.tech/tags/partners-ecosystems.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [twilio](<https://devfeed.tech/tags/twilio.md>), [whatsapp](<https://devfeed.tech/tags/whatsapp.md>)

### AI overview

The article recommends a phased Tyntec-to-Twilio migration to keep customer messaging running: prioritize OTP and transactional traffic, export sender IDs, templates, delivery data and consent records, start required sender registrations early, run both platforms in parallel, then shift traffic gradually while monitoring delivery. It says Meta's WhatsApp migration path preserves the number's display name, messaging tier, quality rating, OBA status and high-quality templates. Twilio's described options include IE1 for EU SMS data residency, Fraud Guard, RCS upgrades, Passkeys and Silent Network Auth; the article also notes that WhatsApp OTP messages are not charged when undelivered. Carrier and regulatory registration approvals may take time. A retailer example describes a two-phase migration with an interim Flex setup in under two weeks, followed by a Twilio Conversations API integration. These claims and steps reflect the supplied article excerpt.

### Source excerpt

Learn how to transition your messaging workflows from Tyntec to Twilio without interruption while maintaining data privacy, WhatsApp reputation, and more.

## Webhooks to Kafka: How to Receive Events and Publish Them to Topics

DevFeed: [Webhooks to Kafka: How to Receive Events and Publish Them to Topics](<https://devfeed.tech/articles/webhooks-to-kafka-how-to-receive-events-and-publish-them-to-topics-121710.md>)

Original publisher: [Read original article](<https://estuary.dev/blog/webhooks-to-kafka>)

Author: Seán Whelan

Published: 2026-11-06T12:27:07Z

Content type: article

Language: en

Sources: [Estuary](<https://devfeed.tech/sources/estuary.md>)

Topics: [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [compare](<https://devfeed.tech/tags/compare.md>), [events](<https://devfeed.tech/tags/events.md>), [gateway](<https://devfeed.tech/tags/gateway.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [http](<https://devfeed.tech/tags/http.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [managed](<https://devfeed.tech/tags/managed.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [retries](<https://devfeed.tech/tags/retries.md>), [webhooks](<https://devfeed.tech/tags/webhooks.md>)

### AI overview

Webhook providers cannot post directly to Kafka, so an HTTPS receiver must verify each request and publish it. The excerpt compares a custom service or HTTP gateway, API Gateway with Lambda, Kafka Connect, and a managed pipeline; the choice depends on operational control, AWS or Connect infrastructure, and who hosts the endpoint. For a direct receiver, verify signatures over raw bytes, produce with the delivery ID as key, and return success only after Kafka acknowledges; provider retries make delivery at least once, so redeliveries can become duplicate messages. Providers have different deadlines and retry behavior--Shopify allows five seconds, while GitHub does not automatically redeliver. Estuary instead acknowledges after committing requests to a durable collection, then materializes them to Kafka independently, allowing capture to continue during a broker outage. Its excerpted limits include a 64 MiB request cap, message truncation thresholds, and signature-header formats that do not support GitHub's or Stripe's built-in formats through the custom setting. The text also covers Kafka size and authentication requirements, recovery, deduplication, and alternate routes.

### Source excerpt

Send webhooks to Kafka with a webhook source connector, an HTTP gateway, AWS Lambda or a managed pipeline. Compare signatures, retries and duplicates.

## How to Use Message Bus DLQs for Advanced Tail-Based Sampling

DevFeed: [How to Use Message Bus DLQs for Advanced Tail-Based Sampling](<https://devfeed.tech/articles/how-to-use-message-bus-dlqs-for-advanced-tail-based-sampling-115704.md>)

Original publisher: [Read original article](<https://hackernoon.com/how-to-use-message-bus-dlqs-for-advanced-tail-based-sampling?source=rss>)

Author: Stephen Tsoi

Published: 2026-11-03T21:13:20Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [abstraction](<https://devfeed.tech/tags/abstraction.md>), [active-active](<https://devfeed.tech/tags/active-active.md>), [addition](<https://devfeed.tech/tags/addition.md>), [agents](<https://devfeed.tech/tags/agents.md>), [all](<https://devfeed.tech/tags/all.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [based](<https://devfeed.tech/tags/based.md>), [bus](<https://devfeed.tech/tags/bus.md>), [collector](<https://devfeed.tech/tags/collector.md>), [dead-letter-queues](<https://devfeed.tech/tags/dead-letter-queues.md>), [design](<https://devfeed.tech/tags/design.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [distributed-tracing](<https://devfeed.tech/tags/distributed-tracing.md>), [eda](<https://devfeed.tech/tags/eda.md>), [event](<https://devfeed.tech/tags/event.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [memory](<https://devfeed.tech/tags/memory.md>), [message](<https://devfeed.tech/tags/message.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [opentelemtry-collector](<https://devfeed.tech/tags/opentelemtry-collector.md>), [point](<https://devfeed.tech/tags/point.md>), [sampling](<https://devfeed.tech/tags/sampling.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [tail-based-sampling](<https://devfeed.tech/tags/tail-based-sampling.md>), [telemetry-pipelines](<https://devfeed.tech/tags/telemetry-pipelines.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The excerpt proposes using a message bus's queue TTL and Dead Letter Queue (DLQ) as the buffer window for OpenTelemetry tail-based sampling. Tier-1 collectors publish spans with mandatory Span Type and Trace ID headers to trace-specific topics; a shared queue retains messages for 30 seconds, then moves unconsumed messages to the DLQ. A tier-2 collector uses an expired root span as a trigger, retrieves spans with the same Trace ID from the active and dead-message queues, applies sampling rules, batches qualified traces to the APM backend, and discards unqualified traces. The buffer duration can be changed dynamically. The design aims to shift buffering and coordination out of collectors, but it is presented as a proposed enterprise pattern, not official OpenTelemetry reference architecture. It also requires message-bus integration and may require custom exporters where broker components are unavailable; Redis or another store is optional for trace metadata and global sampling settings.

### Source excerpt

Discover how to eliminate OpenTelemetry memory bottlenecks by replacing point-to-point collector connections with an Event-Driven Architecture (EDA) design.

## Getting a Grip: Operating Human-Agent Software Teams Through Governed Messages

DevFeed: [Getting a Grip: Operating Human-Agent Software Teams Through Governed Messages](<https://devfeed.tech/articles/getting-a-grip-operating-human-agent-software-teams-through-governed-messages-113493.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.00689>)

Author: Michael Granitzer, Kanishka Ghosh Dastidar, Andreas Einwiller, Jelena Mitrovi\\'c, Saber Zerhoudi

Published: 2026-11-03T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Software Engineering](<https://devfeed.tech/sources/arxiv-software-engineering.md>)

Topics: [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [agent to agent communication](<https://devfeed.tech/topics/agent-to-agent-communication.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [decision-making](<https://devfeed.tech/topics/decision-making.md>), [experience report](<https://devfeed.tech/topics/experience-report.md>), [human review](<https://devfeed.tech/topics/human-review.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agent-software](<https://devfeed.tech/tags/agent-software.md>), [agents](<https://devfeed.tech/tags/agents.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [attention](<https://devfeed.tech/tags/attention.md>), [backdoor](<https://devfeed.tech/tags/backdoor.md>), [coding](<https://devfeed.tech/tags/coding.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [context](<https://devfeed.tech/tags/context.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [decision-making](<https://devfeed.tech/tags/decision-making.md>), [decision-rules](<https://devfeed.tech/tags/decision-rules.md>), [defense](<https://devfeed.tech/tags/defense.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [distributed-system](<https://devfeed.tech/tags/distributed-system.md>), [failure](<https://devfeed.tech/tags/failure.md>), [messages](<https://devfeed.tech/tags/messages.md>), [software](<https://devfeed.tech/tags/software.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

The paper proposes yoars, a relay that governs human-agent software teams through authenticated identities, typed and addressed messages, room-level rules, and an attributable append-only record. Across 899 analyzable controlled runs, changing which messages trigger work and limiting repeated messages coincided with coordination failures falling from 42% to 13%; the adjusted result across nine tests was borderline (p = .057). Role instructions and votes did not reliably enforce process, and conversational defenses did not reliably stop backdoors. Record auditing identified the persuader in all 25 confirmed cases where an attacker recruited a teammate, but also flagged 24 of 40 honest runs. In a four-week deployment involving up to 19 agents and two people, requests mainly waited on the human coordinator and approvals, while agents responded within minutes. The authors identify human attention and context retention as constraints, report instrument failures, and release study materials.

### Source excerpt

arXiv:2611.00689v1 Announce Type: new Abstract: Software is increasingly developed by teams in which several people direct many coding agents from different vendors. Such teams must establish who may request what from whom, which messages start work, which decisions bind, and who caused a change. We propose to govern a human-agent team through its message protocol and present yoars, a relay in which humans and agents are authenticated principals that exchange typed, addressed messages in rooms holding goals, decision rules, routing and an attributable, append-only record. This report gives the architecture, the full controlled study and the field material. In 926 controlled runs (899 analyzable), small agent teams built programs under varied room rules, some with a hostile member planting a backdoor. Revising which messages start work, bundled with limits on repeated messages, was followed by a drop in total coordination failure from 42% to 13% (p = .0063, adjusted p = .057 over nine registered tests). Instructed roles and votes did not reliably produce the intended process, and no defense inside the conversation reliably prevented the backdoor. An auditor read the records of 96 runs with a confirmed backdoor. In the 25 runs where the attacker had persuaded a teammate to write it, the auditor named the persuader in all 25, but it also flagged 24 of 40 honest runs. In a four-week field study, up to nineteen agents and two people developed a distributed system through yoars, producing 7,457 acts. Human attention and decision making emerged as the critical resource: requests waited mainly for the human-run coordinator and for approvals, while agents answered within minutes. Most governance requirements emerged from operation, and holding context dominated token cost. We report twenty-six failures of our own instruments, derive seven lessons and a checklist, and release the corpus, the redacted room ledger and the analysis scripts.

## Building Smaller, Safer Symfony Messenger Queues With Compression and Encryption

DevFeed: [Building Smaller, Safer Symfony Messenger Queues With Compression and Encryption](<https://devfeed.tech/articles/building-smaller-safer-symfony-messenger-queues-with-compression-and-encryption-113688.md>)

Original publisher: [Read original article](<https://hackernoon.com/building-smaller-safer-symfony-messenger-queues-with-compression-and-encryption?source=rss>)

Author: MattLeads

Published: 2026-11-03T04:51:38Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [Compression](<https://devfeed.tech/topics/compression.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>)

Tags: [compression](<https://devfeed.tech/tags/compression.md>), [encryption](<https://devfeed.tech/tags/encryption.md>), [guide](<https://devfeed.tech/tags/guide.md>), [keys](<https://devfeed.tech/tags/keys.md>), [messenger](<https://devfeed.tech/tags/messenger.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [php](<https://devfeed.tech/tags/php.md>), [pii](<https://devfeed.tech/tags/pii.md>), [practical](<https://devfeed.tech/tags/practical.md>), [programming](<https://devfeed.tech/tags/programming.md>), [queues](<https://devfeed.tech/tags/queues.md>), [security](<https://devfeed.tech/tags/security.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [symfony](<https://devfeed.tech/tags/symfony.md>), [symfony-messenger](<https://devfeed.tech/tags/symfony-messenger.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

mattleads/messenger-compress-bundle wraps Symfony Messenger's serializer to compress and encrypt messages at the transport layer while handlers still receive ordinary PHP objects. Configure per-transport or globally; compression can be explicit or automatic above a threshold, and automatic policies retain compressed data only when it is smaller. Encryption uses XChaCha20-Poly1305; bodies are protected, but headers remain readable, so secrets belong in message bodies rather than stamps. Compression runs before encryption, and the article cautions that observable compressed ciphertext length can leak information when attacker-controlled input and secrets share a message. For key rotation, deploy the new key to consumers first, switch producers' active key, then retain the old key until queues and failure transports have cycled. Authentication failures are rejected and follow Messenger retries; failed messages can be replayed after the needed key is installed. The guide targets PHP 8.2+ and Symfony 6.4-8.x; zstd additionally requires ext-zstd.

### Source excerpt

A practical guide to mattleads/messenger-compress-bundle: compress big Symfony Messenger payloads, encrypt PII at rest and rotate keys without draining queues.

## Send your first email, SMS or push with Appwrite Messaging

DevFeed: [Send your first email, SMS or push with Appwrite Messaging](<https://devfeed.tech/articles/send-your-first-email-sms-or-push-with-appwrite-messaging-115768.md>)

Original publisher: [Read original article](<https://appwrite.io/blog/post/send-your-first-message-with-appwrite-messaging>)

Author: Atharva Deosthale

Published: 2026-11-03T00:00:00Z

Content type: tutorial

Language: en

Sources: [Appwrite Blog](<https://devfeed.tech/sources/appwrite-blog.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [email](<https://devfeed.tech/topics/email.md>), [Appwrite](<https://devfeed.tech/topics/appwrite.md>), [Push Notifications](<https://devfeed.tech/topics/push-notifications.md>), [SendGrid](<https://devfeed.tech/topics/sendgrid.md>)

Tags: [amazon-ses](<https://devfeed.tech/tags/amazon-ses.md>), [api](<https://devfeed.tech/tags/api.md>), [app](<https://devfeed.tech/tags/app.md>), [apple](<https://devfeed.tech/tags/apple.md>), [connect](<https://devfeed.tech/tags/connect.md>), [console](<https://devfeed.tech/tags/console.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [device](<https://devfeed.tech/tags/device.md>), [digest](<https://devfeed.tech/tags/digest.md>), [docs](<https://devfeed.tech/tags/docs.md>), [domain](<https://devfeed.tech/tags/domain.md>), [draft](<https://devfeed.tech/tags/draft.md>), [email](<https://devfeed.tech/tags/email.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [first](<https://devfeed.tech/tags/first.md>), [guide](<https://devfeed.tech/tags/guide.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [send](<https://devfeed.tech/tags/send.md>), [sms](<https://devfeed.tech/tags/sms.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>), [users](<https://devfeed.tech/tags/users.md>)

### AI overview

Appwrite Messaging uses connected delivery providers to send email, SMS, and push through one API. To send a first email without changing app code, connect an email service in the Console using its credentials and a sender address on a domain verified with that service, then create a message, select a user with an email address, and send it. "Sent" means the provider accepted the email; the Console also shows when it went out. For one message to many users, create a topic and add subscribers. SMS requires an SMS provider and users with phone numbers. Push additionally requires the app to register each device. Messages can be scheduled in the Console or through a server SDK using a future `scheduledAt` value.

### Source excerpt

Connect an email provider and send your first email to one of your users from the Appwrite Console, then add SMS and push when your app needs them.

## CVE-2026-119736 - Attendo Admin Android 3.0.13 Hard-coded MQTT Broker Credentials

DevFeed: [CVE-2026-119736 - Attendo Admin Android 3.0.13 Hard-coded MQTT Broker Credentials](<https://devfeed.tech/articles/cve-2026-119736-attendo-admin-android-3-0-13-hard-coded-mqtt-broker-credentials-112590.md>)

Original publisher: [Read original article](<https://cvefeed.io/vuln/detail/CVE-2026-119736>)

Author: CVEFEED.io; vulncheck.com

Published: 2026-11-02T19:18:02Z

Content type: news

Language: en

Sources: [Latest High/Critical Vulnerabilitiy Feed](<https://devfeed.tech/sources/latest-high-critical-vulnerabilitiy-feed.md>)

Topics: [hardcoded credentials](<https://devfeed.tech/topics/hardcoded-credentials.md>), [MQTT](<https://devfeed.tech/topics/mqtt.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [credential-based attacks](<https://devfeed.tech/topics/credential-based-attacks.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [android](<https://devfeed.tech/tags/android.md>), [apk](<https://devfeed.tech/tags/apk.md>), [application](<https://devfeed.tech/tags/application.md>), [assets](<https://devfeed.tech/tags/assets.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [base64](<https://devfeed.tech/tags/base64.md>), [broker](<https://devfeed.tech/tags/broker.md>), [command](<https://devfeed.tech/tags/command.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-119736](<https://devfeed.tech/tags/cve-2026-119736.md>), [data](<https://devfeed.tech/tags/data.md>), [device](<https://devfeed.tech/tags/device.md>), [employee](<https://devfeed.tech/tags/employee.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [json](<https://devfeed.tech/tags/json.md>), [message](<https://devfeed.tech/tags/message.md>), [mqtt](<https://devfeed.tech/tags/mqtt.md>)

### AI overview

Attendo (formerly Petpooja Payroll) Admin for Android versions 3.0.13 and earlier is described as embedding production MQTT broker credentials in Flutter configuration assets. The description says an attacker could recover them by decompiling the APK, connect to the broker over TCP 1883, access topics containing attendance data, personal identifiers, photos, device telemetry, and authentication material, and publish messages, creating risks of data exposure and unauthorized message injection. The page gives a severity score of 8.8 (High); its affected-products table has no product record, and it provides no further technical details in the supplied text.

### Source excerpt

CVE ID :CVE-2026-119736 Published : Nov. 2, 2026, 7:18 p.m. | 47 minutes ago Description :Attendo (formerly Petpooja Payroll) Admin Android application version 3.0.13 and earlier contains a hard-coded credentials vulnerability that allows attackers to extract production MQTT broker credentials by decompiling the APK's bundled Flutter configuration assets such as production.json and device-command configuration files. Attackers can use the recovered credentials to authenticate to the production MQTT broker over TCP 1883, access messaging topics containing employee attendance records, personal identifiers, Base64-encoded photographs, device telemetry, and authentication material, and publish messages to those topics, resulting in exposure of sensitive data and potential unauthorized message injection. Severity: 8.8 | HIGH Visit the link for more details, such as CVSS details, affected products, timeline, and more...

## Sampling Ad Exchange Events at Scale: What We Kept, What We Dropped, and Why

DevFeed: [Sampling Ad Exchange Events at Scale: What We Kept, What We Dropped, and Why](<https://devfeed.tech/articles/sampling-ad-exchange-events-at-scale-what-we-kept-what-we-dropped-and-why-112261.md>)

Original publisher: [Read original article](<https://hackernoon.com/sampling-ad-exchange-events-at-scale-what-we-kept-what-we-dropped-and-why?source=rss>)

Author: Vikrant Bachhav

Published: 2026-11-02T06:00:04Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Big data infrastructure](<https://devfeed.tech/topics/big-data-infrastructure.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [Apache Spark](<https://devfeed.tech/topics/spark.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Grafana](<https://devfeed.tech/topics/grafana.md>)

Tags: [2019](<https://devfeed.tech/tags/2019.md>), [2022](<https://devfeed.tech/tags/2022.md>), [2023](<https://devfeed.tech/tags/2023.md>), [adtech](<https://devfeed.tech/tags/adtech.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [bi](<https://devfeed.tech/tags/bi.md>), [big-data](<https://devfeed.tech/tags/big-data.md>), [billing](<https://devfeed.tech/tags/billing.md>), [business](<https://devfeed.tech/tags/business.md>), [click](<https://devfeed.tech/tags/click.md>), [cloud-cost-optimization](<https://devfeed.tech/tags/cloud-cost-optimization.md>), [costs](<https://devfeed.tech/tags/costs.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-pipelines](<https://devfeed.tech/tags/data-pipelines.md>), [data-sampling-techniques](<https://devfeed.tech/tags/data-sampling-techniques.md>), [events](<https://devfeed.tech/tags/events.md>), [exchange](<https://devfeed.tech/tags/exchange.md>), [executor](<https://devfeed.tech/tags/executor.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [reporting](<https://devfeed.tech/tags/reporting.md>), [sampling](<https://devfeed.tech/tags/sampling.md>), [scale](<https://devfeed.tech/tags/scale.md>), [spark](<https://devfeed.tech/tags/spark.md>), [stream](<https://devfeed.tech/tags/stream.md>), [unity](<https://devfeed.tech/tags/unity.md>), [volume](<https://devfeed.tech/tags/volume.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

Unity reduced ad exchange stream volume from about 10 GB/s to 2 GB/s by sampling pre-filter events at 0.5% while retaining post-filter events at full fidelity. Sampling by auction ID kept related events joinable; counts from sampled data were scaled by the inverse sampling probability, while ratios remained comparable when both parts used the same sample. After reviewing reporting needs with report owners, the team moved reports to a separate sampled Kafka topic and tuned Spark executors. Worker count fell from 240 to 30 and CPU utilization rose 41%; DSP Report transform billing was about 41% lower for March 9-April 6, 2023 than the prior period. Two weeks of parallel comparisons preceded report cutover. Validation also uncovered longstanding join duplication that inflated BidWin and WinPrice metrics. The account notes that dimensions considered unsafe to sample were kept at full fidelity.

### Source excerpt

How we reduced Kafka stream volume by 80%, cut Spark workers from 240 to 30, and lowered reporting costs through sampling and executor tuning at Unity.

## Message Queues

DevFeed: [Message Queues](<https://devfeed.tech/articles/message-queues-111142.md>)

Original publisher: [Read original article](<https://blog.alexewerlof.com/p/message-queues>)

Author: Alex Ewerlöf

Published: 2026-11-02T05:30:53Z

Content type: article

Language: en

Sources: [Alex Ewerlof Notes](<https://devfeed.tech/sources/alex-ewerlof-notes.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [decoupling](<https://devfeed.tech/topics/decoupling.md>), [backpressure](<https://devfeed.tech/topics/backpressure.md>), [scalable-architecture](<https://devfeed.tech/topics/scalable-architecture.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [admin](<https://devfeed.tech/tags/admin.md>), [ads](<https://devfeed.tech/tags/ads.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alerting](<https://devfeed.tech/tags/alerting.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [all](<https://devfeed.tech/tags/all.md>), [allows](<https://devfeed.tech/tags/allows.md>), [also](<https://devfeed.tech/tags/also.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [message](<https://devfeed.tech/tags/message.md>), [message-queues](<https://devfeed.tech/tags/message-queues.md>), [queues](<https://devfeed.tech/tags/queues.md>), [resilient-architecture](<https://devfeed.tech/tags/resilient-architecture.md>)

### AI overview

Message queues let producers hand work to separate consumers, shortening user-facing waits, isolating worker failures, and buffering traffic spikes. Consumers acknowledge completed messages; if a worker fails before acknowledging, messages can be redelivered, so at-least-once delivery may cause duplicates and works best with idempotent processing. The text recommends queues for asynchronous work, bursty traffic, decoupled scaling, and reliability, while warning they add latency to time-sensitive synchronous workloads. It explains partitioning, ordering versus even workload distribution, back pressure, retry limits and dead letter queues, and durable storage with replay. Kafka retains messages for a configured period and scales through partitions and consumer groups; SQS is managed and offers Standard queues with best-effort ordering or FIFO queues with strict ordering and lower throughput; RabbitMQ uses exchanges and bindings for complex routing.

### Source excerpt

Part of resilient architecture patterns series

## Podcast: AI, ML, and Data Engineering InfoQ Trends Report 2026

DevFeed: [Podcast: AI, ML, and Data Engineering InfoQ Trends Report 2026](<https://devfeed.tech/articles/podcast-ai-ml-and-data-engineering-infoq-trends-report-2026-107542.md>)

Original publisher: [Read original article](<https://www.infoq.com/podcasts/ai-ml-data-engineering-trends-2026/>)

Author: Chip Huyen, Daniel Dominguez, Hien Luu, Arthur Casals

Published: 2026-10-30T09:00:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Machine learning](<https://devfeed.tech/topics/machine-learning.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Robotics](<https://devfeed.tech/topics/robotics.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [llm-reasoning](<https://devfeed.tech/topics/llm-reasoning.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [codex](<https://devfeed.tech/topics/codex.md>), [InfoQ](<https://devfeed.tech/topics/infoq.md>), [AI for customer service automation](<https://devfeed.tech/topics/ai-for-customer-service-automation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agent2agent](<https://devfeed.tech/tags/agent2agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted-coding](<https://devfeed.tech/tags/ai-assisted-coding.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-development](<https://devfeed.tech/tags/ai-development.md>), [ai-evals](<https://devfeed.tech/tags/ai-evals.md>), [ai-evaluations](<https://devfeed.tech/tags/ai-evaluations.md>), [ai-factory](<https://devfeed.tech/tags/ai-factory.md>), [ai-harness](<https://devfeed.tech/tags/ai-harness.md>), [ai-ml](<https://devfeed.tech/tags/ai-ml.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [ai-ml-data-engineering-trends-2026](<https://devfeed.tech/tags/ai-ml-data-engineering-trends-2026.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [context-engineering](<https://devfeed.tech/tags/context-engineering.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [frontier-model](<https://devfeed.tech/tags/frontier-model.md>), [infoq](<https://devfeed.tech/tags/infoq.md>), [infoq-trends-report](<https://devfeed.tech/tags/infoq-trends-report.md>), [infoq-trends-report-2026](<https://devfeed.tech/tags/infoq-trends-report-2026.md>), [large-language-models](<https://devfeed.tech/tags/large-language-models.md>), [ml](<https://devfeed.tech/tags/ml.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [multi-model-databases](<https://devfeed.tech/tags/multi-model-databases.md>), [podcast](<https://devfeed.tech/tags/podcast.md>), [report](<https://devfeed.tech/tags/report.md>), [robotics](<https://devfeed.tech/tags/robotics.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [spec-driven-development](<https://devfeed.tech/tags/spec-driven-development.md>), [the-infoq-podcast](<https://devfeed.tech/tags/the-infoq-podcast.md>), [trends](<https://devfeed.tech/tags/trends.md>)

### AI overview

The panel sees AI in 2026 shifting from model capability toward reliable systems that match models to workloads and can operate in real workflows. They describe a move toward smaller, cheaper models alongside reasoning models, distillation and quantization; organizations weigh capability, latency, cost and data boundaries, while fine-tuning remains costly and operationally demanding. Agents are expanding from personal assistants to team and organization workflows, raising needs for permissions, auditability, context and memory management, runtime support, and coordination. For production agents, evaluation should cover the whole system--including tools, context and environment--and measure task completion, cost, duration, interventions and unsafe actions. Physical AI extends these concerns to robots and other machines, where errors have physical consequences and safety, simulation and verification matter. The discussion is a trends conversation, not a comprehensive technical guide.

### Source excerpt

In this episode, members of the InfoQ AI and ML editorial staff and friends of InfoQ discuss the current trends in the domain of AI, ML and Data Engineering. One of the regular features of InfoQ are the trends reports, which each focus on a different aspect of software dev. These reports provide the InfoQ readers and listeners with a high-level overview of the topics to pay attention to this year. By Chip Huyen, Daniel Dominguez, Hien Luu, Arthur Casals

## New in Symfony 8.2: Cross-Application Messaging

DevFeed: [New in Symfony 8.2: Cross-Application Messaging](<https://devfeed.tech/articles/new-in-symfony-8-2-cross-application-messaging-106096.md>)

Original publisher: [Read original article](<https://symfony.com/blog/new-in-symfony-8-2-cross-application-messaging>)

Author: Javier Eguiluz

Published: 2026-10-29T08:30:00Z

Content type: tutorial

Language: en

Sources: [Symfony](<https://devfeed.tech/sources/symfony-blog.md>)

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [RabbitMQ](<https://devfeed.tech/topics/rabbitmq.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [cross](<https://devfeed.tech/tags/cross.md>), [except](<https://devfeed.tech/tags/except.md>), [go](<https://devfeed.tech/tags/go.md>), [json](<https://devfeed.tech/tags/json.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [php](<https://devfeed.tech/tags/php.md>), [rabbitmq](<https://devfeed.tech/tags/rabbitmq.md>), [symfony](<https://devfeed.tech/tags/symfony.md>)

### AI overview

Symfony 8.2 adds an interop serializer for Messenger transports shared with applications that may use different configurations or languages. It omits stamps when sending and ignores incoming stamps, avoiding failures from unavailable stamp classes or bus names; retry and failure-transport messages retain stamps for retry counting. Messages use a JSON body and plain headers. The default `type` header is a PHP class name, so cross-application consumers can use a shared serialized type name; for a single-message transport, configure the class explicitly, or provide a closure to determine types for multiple messages. The serializer maps message ID, correlation, and causation stamps to headers when `identity_stamps` is enabled, and custom mappers can expose other stamp data. Signatures include serializer-written headers except `Content-Type`, including mapped headers, but exclude headers added later. Applications consuming signed transports must be upgraded before senders because Symfony 7.4.18+ and 8.1.6+ reject signed messages with headers outside the listed allowlist.

### Source excerpt

Messenger transports often connect your Symfony application to other applications, which may not use Symfony or even PHP. For example, a shop publishes its orders to RabbitMQ and an invoicing service written in Go consumes them. Symfony 8.2 adds a new serializer...

## How to make postMessage type-safe in under 350 bytes

DevFeed: [How to make postMessage type-safe in under 350 bytes](<https://devfeed.tech/articles/how-to-make-postmessage-type-safe-in-under-350-bytes-105920.md>)

Original publisher: [Read original article](<https://evilmartians.com/chronicles/how-to-make-postmessage-type-safe-in-under-350-bytes>)

Author: Travis Turner (richardturner@evilmartians.com)

Published: 2026-10-28T00:00:00Z

Content type: article

Language: en

Sources: [Evil Martians](<https://devfeed.tech/sources/evil-martians.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [union types](<https://devfeed.tech/topics/union-types.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [brotli](<https://devfeed.tech/tags/brotli.md>), [bus](<https://devfeed.tech/tags/bus.md>), [cancellation](<https://devfeed.tech/tags/cancellation.md>), [channel](<https://devfeed.tech/tags/channel.md>), [cleanup](<https://devfeed.tech/tags/cleanup.md>), [dependencies](<https://devfeed.tech/tags/dependencies.md>), [dx](<https://devfeed.tech/tags/dx.md>), [errors](<https://devfeed.tech/tags/errors.md>), [events](<https://devfeed.tech/tags/events.md>), [iframes](<https://devfeed.tech/tags/iframes.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [library](<https://devfeed.tech/tags/library.md>), [messages](<https://devfeed.tech/tags/messages.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [postmessage](<https://devfeed.tech/tags/postmessage.md>), [type-safe](<https://devfeed.tech/tags/type-safe.md>), [typescript](<https://devfeed.tech/tags/typescript.md>), [workers](<https://devfeed.tech/tags/workers.md>)

### AI overview

typed-channel gives TypeScript-checked message names and payloads across workers, iframes, tabs, and in-page event buses, using a shared channel API with interchangeable transports. Its `on` method returns an unsubscribe function; custom transports need only `on` and `emit`. The excerpt reports a 341-byte core with the `postMessage` transport and no dependencies. Version 0.11 adds optional RPC through `createTypedRpcChannel`: typed requests and handlers, propagated errors, and `AbortSignal` cancellation that stops handler work. Requests without a matching handler do not resolve on their own, so callers should provide a timeout signal when needed. Payloads and results are structured-cloned without library validation. `unlisten()` disconnects transports and rejects pending requests while aborting corresponding remote work. The RPC factory is about 1 kB; one-way messaging remains separate so projects pay for RPC only when used.

### Source excerpt

Typed-channel is a library for typed messages and requests across workers, iframes, tabs, and event buses.

## Event-Driven CI at Enterprise Scale: Decoupling Webhook Ingestion with Kafka

DevFeed: [Event-Driven CI at Enterprise Scale: Decoupling Webhook Ingestion with Kafka](<https://devfeed.tech/articles/event-driven-ci-at-enterprise-scale-decoupling-webhook-ingestion-with-kafka-98462.md>)

Original publisher: [Read original article](<https://hackernoon.com/event-driven-ci-at-enterprise-scale-decoupling-webhook-ingestion-with-kafka?source=rss>)

Author: Vidhi Shah

Published: 2026-10-23T21:08:58Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [event driven](<https://devfeed.tech/topics/event-driven.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Chaos Engineering](<https://devfeed.tech/topics/chaos-engineering.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [availability](<https://devfeed.tech/tags/availability.md>), [ci](<https://devfeed.tech/tags/ci.md>), [cicd](<https://devfeed.tech/tags/cicd.md>), [decoupling](<https://devfeed.tech/tags/decoupling.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [event](<https://devfeed.tech/tags/event.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [github](<https://devfeed.tech/tags/github.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [partition](<https://devfeed.tech/tags/partition.md>), [production](<https://devfeed.tech/tags/production.md>), [queues](<https://devfeed.tech/tags/queues.md>), [scale](<https://devfeed.tech/tags/scale.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [stateless](<https://devfeed.tech/tags/stateless.md>), [webhook](<https://devfeed.tech/tags/webhook.md>)

### AI overview

The article's main finding is that adding runners does not absorb synchronized webhook bursts; separating ingestion from build scheduling does. Its design uses stateless receivers to verify GitHub signatures and wait for durable Kafka acknowledgment, then partitions events by organization, repository, and ref so each ref stays ordered while different refs run in parallel. Consumers schedule builds with idempotent job keys, deduplicate delivery IDs, recheck authorization at execution, and commit offsets only after processing; a dead-letter queue, consumer-lag monitoring, backpressure, and reconciliation address failures and missed deliveries. The authors report 128 partitions for roughly 2,500 scheduling events per second. They caution that rebalances can halt affected partitions, so autoscaling should be gradual with cooldowns. This adds status delay and makes Kafka a critical dependency; the article says synchronous CI remains simpler and more economical for modest workloads.

### Source excerpt

Decouple CI webhook ingestion with Kafka: stateless receivers, per-ref partition keys, idempotent consumers, dead-letter queues, and production lessons.

## Replacing Transactional MSMQ with RabbitMQ Without Losing Consistency

DevFeed: [Replacing Transactional MSMQ with RabbitMQ Without Losing Consistency](<https://devfeed.tech/articles/replacing-transactional-msmq-with-rabbitmq-without-losing-consistency-97413.md>)

Original publisher: [Read original article](<https://hackernoon.com/replacing-transactional-msmq-with-rabbitmq-without-losing-consistency?source=rss>)

Author: Ilnur Yusupov

Published: 2026-10-23T08:31:42Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [RabbitMQ](<https://devfeed.tech/topics/rabbitmq.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [consistency](<https://devfeed.tech/topics/consistency.md>), [acid](<https://devfeed.tech/topics/acid.md>), [schema-evolution](<https://devfeed.tech/topics/schema-evolution.md>)

Tags: [consistency](<https://devfeed.tech/tags/consistency.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [msmq](<https://devfeed.tech/tags/msmq.md>), [msmq-to-rabbitmq-migration](<https://devfeed.tech/tags/msmq-to-rabbitmq-migration.md>), [net](<https://devfeed.tech/tags/net.md>), [net-framework](<https://devfeed.tech/tags/net-framework.md>), [outbox](<https://devfeed.tech/tags/outbox.md>), [outbox-pattern](<https://devfeed.tech/tags/outbox-pattern.md>), [rabbitmq](<https://devfeed.tech/tags/rabbitmq.md>), [sql-server-transactions](<https://devfeed.tech/tags/sql-server-transactions.md>)

### AI overview

A direct MSMQ-to-RabbitMQ swap loses the atomicity that System.Transactions and MSDTC can provide across SQL Server and transactional MSMQ. Publishing before the SQL commit can expose an event for rolled-back data; publishing afterward can leave committed data without an event. The outbox addresses this dual-write gap by recording the business change and outgoing message in one database transaction, then dispatching to RabbitMQ asynchronously with publisher confirms and retries. A crash after broker confirmation but before marking the outbox row can cause duplicate publication, so consumers need idempotent processing, such as storing MessageId with business updates in one transaction. This replaces coordinated distributed transactions with eventual consistency and at-least-once delivery. The article also outlines operational needs such as concurrent row claiming, backoff, ordering, poison-message handling, monitoring, and cleanup, and recommends isolating messaging changes from runtime migration.

### Source excerpt

Learn why replacing transactional MSMQ with RabbitMQ changes consistency guarantees and how the outbox pattern helps preserve reliable messaging. TL;DR: Repla

## Helidon 27 Introduces Restructured Programming Models and New Messaging and Data Modules

DevFeed: [Helidon 27 Introduces Restructured Programming Models and New Messaging and Data Modules](<https://devfeed.tech/articles/helidon-27-introduces-restructured-programming-models-and-new-messaging-and-data-modules-88463.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/helidon-27-released/>)

Author: Michael Redlich

Published: 2026-10-16T11:20:00Z

Content type: release

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Spring Framework](<https://devfeed.tech/topics/spring-framework.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [applications](<https://devfeed.tech/tags/applications.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [concurrent](<https://devfeed.tech/tags/concurrent.md>), [database](<https://devfeed.tech/tags/database.md>), [dependency-injection](<https://devfeed.tech/tags/dependency-injection.md>), [developers](<https://devfeed.tech/tags/developers.md>), [development](<https://devfeed.tech/tags/development.md>), [features](<https://devfeed.tech/tags/features.md>), [helidon](<https://devfeed.tech/tags/helidon.md>), [helidon-27-released](<https://devfeed.tech/tags/helidon-27-released.md>), [helidon-nima](<https://devfeed.tech/tags/helidon-nima.md>), [java](<https://devfeed.tech/tags/java.md>), [java-verified-portfolio](<https://devfeed.tech/tags/java-verified-portfolio.md>), [jdbc](<https://devfeed.tech/tags/jdbc.md>), [jdk](<https://devfeed.tech/tags/jdk.md>), [jdk-27](<https://devfeed.tech/tags/jdk-27.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [modules](<https://devfeed.tech/tags/modules.md>), [new-features](<https://devfeed.tech/tags/new-features.md>), [news](<https://devfeed.tech/tags/news.md>), [open-jdk](<https://devfeed.tech/tags/open-jdk.md>), [programming](<https://devfeed.tech/tags/programming.md>), [release](<https://devfeed.tech/tags/release.md>), [stable](<https://devfeed.tech/tags/stable.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

Helidon 27 introduces a new Helidon Core with Imperative and Declarative programming models, plus Helidon Messaging and Helidon Data JDBC. The release follows Oracle's Tip & Tail library development model: Helidon 27 adopts JDK 27, while Helidon 4.5.5 maintains a longer-lived JDK 21 baseline with JDK 25 support and selected fixes and backports.

### Source excerpt

The release of Helidon 27 is the first release that follows the Oracle Tip & Tail Model of Library Development by which the Tip adopts the latest Java technology while the Tail provides a more stable and secure baseline. Concurrent with the release of JDK 27, new features in Helidon 27 include: an introduction to new major modules, Helidon Messaging and Helidon Data JDBC. By Michael Redlich

## Message Queues Explained: How They Work & Why

DevFeed: [Message Queues Explained: How They Work & Why](<https://devfeed.tech/articles/message-queues-explained-how-they-work-why-87507.md>)

Original publisher: [Read original article](<https://talent500.com/blog/message-queues/>)

Author: Kashif Khan

Published: 2026-10-15T02:16:52Z

Content type: tutorial

Language: en

Sources: [Talent500](<https://devfeed.tech/sources/backend-archives-talent500-blog.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [Amazon Simple Queue Service (SQS)](<https://devfeed.tech/topics/amazon-simple-queue-service-sqs.md>), [RabbitMQ](<https://devfeed.tech/topics/rabbitmq.md>)

Tags: [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [apache](<https://devfeed.tech/tags/apache.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [asynchronous-communication](<https://devfeed.tech/tags/asynchronous-communication.md>), [azure-service-bus](<https://devfeed.tech/tags/azure-service-bus.md>), [backend](<https://devfeed.tech/tags/backend.md>), [background-job-processing](<https://devfeed.tech/tags/background-job-processing.md>), [benefits-of-message-queues](<https://devfeed.tech/tags/benefits-of-message-queues.md>), [dead-letter-queue](<https://devfeed.tech/tags/dead-letter-queue.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event-streaming](<https://devfeed.tech/tags/event-streaming.md>), [google-cloud-pub-sub](<https://devfeed.tech/tags/google-cloud-pub-sub.md>), [how-message-queues-work](<https://devfeed.tech/tags/how-message-queues-work.md>), [message-broker](<https://devfeed.tech/tags/message-broker.md>), [message-prioritization](<https://devfeed.tech/tags/message-prioritization.md>), [message-producers-and-consumers](<https://devfeed.tech/tags/message-producers-and-consumers.md>), [message-queue](<https://devfeed.tech/tags/message-queue.md>), [message-queue-components](<https://devfeed.tech/tags/message-queue-components.md>), [message-queue-implementation](<https://devfeed.tech/tags/message-queue-implementation.md>), [message-queue-vs-database](<https://devfeed.tech/tags/message-queue-vs-database.md>), [message-queue-vs-message-bus](<https://devfeed.tech/tags/message-queue-vs-message-bus.md>), [message-queue-vs-pub-sub](<https://devfeed.tech/tags/message-queue-vs-pub-sub.md>), [message-queue-vs-web-services](<https://devfeed.tech/tags/message-queue-vs-web-services.md>), [message-queues](<https://devfeed.tech/tags/message-queues.md>), [message-queuing-as-a-service](<https://devfeed.tech/tags/message-queuing-as-a-service.md>), [message-routing](<https://devfeed.tech/tags/message-routing.md>), [microservices-messaging](<https://devfeed.tech/tags/microservices-messaging.md>), [point-to-point-messaging](<https://devfeed.tech/tags/point-to-point-messaging.md>), [publish-subscribe-messaging](<https://devfeed.tech/tags/publish-subscribe-messaging.md>), [python-message-queue](<https://devfeed.tech/tags/python-message-queue.md>), [queues](<https://devfeed.tech/tags/queues.md>), [rabbitmq](<https://devfeed.tech/tags/rabbitmq.md>), [types-of-message-queues](<https://devfeed.tech/tags/types-of-message-queues.md>)

### AI overview

This tutorial explains message queues as a way for applications and services to communicate asynchronously. It covers producers, consumers, routing, acknowledgements, retries, dead letter queues, queue and publish-subscribe models, and uses such as background jobs and microservices. It also introduces Kafka and managed cloud messaging services.

### Source excerpt

A message queue enables applications and services to exchange data asynchronously without depending on immediate responses. Explore how message queues work, their types, key components, benefits, and popular tools like RabbitMQ, Apache Kafka, and Amazon SQS for building scalable, reliable systems. The post Message Queues Explained: How They Work & Why appeared first on Talent500 blog.

## AWS Introduces Enhanced Custom Event Buses for EventBridge

DevFeed: [AWS Introduces Enhanced Custom Event Buses for EventBridge](<https://devfeed.tech/articles/aws-introduces-enhanced-custom-event-buses-for-eventbridge-84693.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/10/aws-enhanced-eventbridge-buses/>)

Author: Renato Losio

Published: 2026-10-11T06:35:00Z

Content type: news

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>)

Tags: [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-enhanced-eventbridge-buses](<https://devfeed.tech/tags/aws-enhanced-eventbridge-buses.md>), [aws-lambda](<https://devfeed.tech/tags/aws-lambda.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-architecture](<https://devfeed.tech/tags/cloud-architecture.md>), [deduplication](<https://devfeed.tech/tags/deduplication.md>), [devops](<https://devfeed.tech/tags/devops.md>), [distributed-systems](<https://devfeed.tech/tags/distributed-systems.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [eventbridge](<https://devfeed.tech/tags/eventbridge.md>), [news](<https://devfeed.tech/tags/news.md>), [publisher](<https://devfeed.tech/tags/publisher.md>), [serverless](<https://devfeed.tech/tags/serverless.md>), [subscriber](<https://devfeed.tech/tags/subscriber.md>)

### AI overview

AWS introduced enhanced custom event buses for Amazon EventBridge, enabling organizations to share a bus across accounts with ordered delivery, event replay, content-based deduplication, and simplified subscriber management. The release also adds JSONata transformations, Avro and Protobuf payload support, and pricing based on event ingress and egress. Existing custom buses remain unchanged.

### Source excerpt

AWS recently announced enhanced custom event buses for Amazon EventBridge, allowing organizations to share a centralized bus across accounts with ordered delivery, simplified subscriber management, event replay, content-based deduplication, and a new publisher/subscriber-based pricing model. By Renato Losio

## LeapXpert brings governed WhatsApp client messaging into Cisco's Webex

DevFeed: [LeapXpert brings governed WhatsApp client messaging into Cisco's Webex](<https://devfeed.tech/articles/leapxpert-brings-governed-whatsapp-client-messaging-into-cisco-s-webex-64893.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/10/05/leapxpert-brings-governed-whatsapp-client-messaging-into-ciscos-webex/>)

Author: Duncan Riley

Published: 2026-10-05T14:00:51Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [in-app experiences](<https://devfeed.tech/topics/in-app-experiences.md>), [Cisco](<https://devfeed.tech/topics/cisco.md>), [Duo](<https://devfeed.tech/topics/duo.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [apps](<https://devfeed.tech/tags/apps.md>), [archiving](<https://devfeed.tech/tags/archiving.md>), [avi-pardo](<https://devfeed.tech/tags/avi-pardo.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cisco-systems](<https://devfeed.tech/tags/cisco-systems.md>), [client-communications](<https://devfeed.tech/tags/client-communications.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [compliance](<https://devfeed.tech/tags/compliance.md>), [customer-support](<https://devfeed.tech/tags/customer-support.md>), [data](<https://devfeed.tech/tags/data.md>), [data-loss-prevention](<https://devfeed.tech/tags/data-loss-prevention.md>), [enterprise-messaging](<https://devfeed.tech/tags/enterprise-messaging.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [governed-communications](<https://devfeed.tech/tags/governed-communications.md>), [integration](<https://devfeed.tech/tags/integration.md>), [leapxpert](<https://devfeed.tech/tags/leapxpert.md>), [lloyds-bank](<https://devfeed.tech/tags/lloyds-bank.md>), [maxen](<https://devfeed.tech/tags/maxen.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-teams](<https://devfeed.tech/tags/microsoft-teams.md>), [news](<https://devfeed.tech/tags/news.md>), [portage-ventures](<https://devfeed.tech/tags/portage-ventures.md>), [riverwood-capital](<https://devfeed.tech/tags/riverwood-capital.md>), [slack](<https://devfeed.tech/tags/slack.md>), [softbank-group](<https://devfeed.tech/tags/softbank-group.md>), [teams](<https://devfeed.tech/tags/teams.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [webex](<https://devfeed.tech/tags/webex.md>), [webex-app-hub](<https://devfeed.tech/tags/webex-app-hub.md>), [webexone-2026](<https://devfeed.tech/tags/webexone-2026.md>), [whatsapp](<https://devfeed.tech/tags/whatsapp.md>)

### AI overview

LeapXpert and Cisco introduced an integration that lets Webex users message clients on WhatsApp within the collaboration app. Messages pass through data loss prevention, and LeapXpert archives the conversations to help organizations govern client communications. The integration is available through the Webex App Hub and requires a Webex license and LeapXpert Work account.

### Source excerpt

Governed communications startup LeapXpert Inc. and Cisco Systems Inc. today unveiled an integration that lets Webex users message clients on WhatsApp without leaving the collaboration app. The integration takes aim at client conversations that compliance teams cannot see. Messaging in Webex has mostly run between colleagues at the same company, and the chats those employees [...] The post LeapXpert brings governed WhatsApp client messaging into Cisco's Webex appeared first on SiliconANGLE.

## Building a Resilient Event-Driven Data Lakehouse: MinIO Bucket Notifications to Apache Kafka

DevFeed: [Building a Resilient Event-Driven Data Lakehouse: MinIO Bucket Notifications to Apache Kafka](<https://devfeed.tech/articles/building-a-resilient-event-driven-data-lakehouse-minio-bucket-notifications-to-apache-kafka-64238.md>)

Original publisher: [Read original article](<https://blog.devops.dev/building-a-resilient-event-driven-data-lakehouse-minio-bucket-notifications-to-apache-kafka-6f8e33267278?source=rss----33f8b2d9a328---4>)

Author: Mobin Shaterian

Published: 2026-10-02T20:11:01Z

Content type: tutorial

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [MinIO](<https://devfeed.tech/topics/minio.md>), [event-driven data processing](<https://devfeed.tech/topics/event-driven-data-processing.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [apache-kafka](<https://devfeed.tech/tags/apache-kafka.md>), [apache-spark](<https://devfeed.tech/tags/apache-spark.md>), [api](<https://devfeed.tech/tags/api.md>), [architectures](<https://devfeed.tech/tags/architectures.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-s3](<https://devfeed.tech/tags/aws-s3.md>), [batch](<https://devfeed.tech/tags/batch.md>), [big-data](<https://devfeed.tech/tags/big-data.md>), [broker](<https://devfeed.tech/tags/broker.md>), [building](<https://devfeed.tech/tags/building.md>), [can](<https://devfeed.tech/tags/can.md>), [data](<https://devfeed.tech/tags/data.md>), [data-lake](<https://devfeed.tech/tags/data-lake.md>), [data-lakehouse](<https://devfeed.tech/tags/data-lakehouse.md>), [event](<https://devfeed.tech/tags/event.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [lakehouse](<https://devfeed.tech/tags/lakehouse.md>), [minio](<https://devfeed.tech/tags/minio.md>), [notifications](<https://devfeed.tech/tags/notifications.md>)

### AI overview

The article proposes using MinIO bucket notifications to signal completed datasets through lightweight Kafka events, avoiding repeated object-store polling and sending large data files through Kafka. To prevent consumers from seeing partially written output, writers upload partitions and a manifest first, then write a `_SUCCESS` marker; MinIO filters for put events with the `_SUCCESS` suffix, and consumers verify the manifest and checksums before processing. The setup example uses SASL_SSL with SCRAM-SHA-512, producer-only Kafka ACLs, a single-partition topic for global FIFO ordering, and MinIO's on-disk queue to retain unsent events during broker outages. Because delivery is at least once, consumers should deduplicate using the event sequencer. The article also recommends monitoring queue length, skipped events, and failed deliveries; a saturated queue can cause event loss.

### Source excerpt

Eliminate object storage polling and prevent race conditions using MinIO's native Kafka notification engine and the Sentinel Marker pattern. Special thanks to mohsen taleb In distributed architectures, few patterns cause as much latency and architectural debt as active polling. Having downstream consumers periodically query an object store like AWS S3 or MinIO to check whether a batch calculation or machine learning dataset has finished is inefficient, difficult to scale, and fraught with timing issues. Conversely, passing entire multi-gigabyte analytical datasets directly through a message broker like Apache Kafka can saturate network interfaces, spike memory usage, and exhaust broker storage. The optimal pattern is Claim-Check / Event-Driven Metadata Notification: the analytical engine writes the bulk data directly into object storage, while the storage layer itself notifies Apache Kafka that the dataset is ready. Downstream consumers simply receive a lightweight event containing the bucket and object path, then fetch only the files they need via standard S3 API primitives. However, there is a catch that catches many teams off guard: the partial read problem. Here is a guide to designing and implementing an enterprise-grade MinIO-to-Kafka event pipeline that solves this problem using the sentinel marker pattern, resilient local queueing, and secure SCRAM authentication. The Partial Read Challenge and the Sentinel Marker Pattern Distributed compute engines -- such as Apache Spark, Flink, Trino, or containerized data workers -- write dataset partitions concurrently across many parallel tasks. A single pipeline run may output dozens of Parquet files alongside a metadata manifest. If you configure MinIO to publish an event on every generic object creation (s3:ObjectCreated:*), your message broker will be flooded with dozens of notifications while the dataset is still being written. Downstream consumers will inevitably attempt to read partitions before the entire dataset

## Introducing Encore x Bird

DevFeed: [Introducing Encore x Bird](<https://devfeed.tech/articles/introducing-encore-bird-63517.md>)

Original publisher: [Read original article](<https://encore.dev/blog/encore-bird>)

Author: Ivan Cernja

Published: 2026-09-29T00:00:00Z

Content type: tutorial

Language: en

Sources: [Encore Updates](<https://devfeed.tech/sources/encore-updates.md>)

Topics: [Messaging](<https://devfeed.tech/topics/messaging.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [cron](<https://devfeed.tech/tags/cron.md>), [database](<https://devfeed.tech/tags/database.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [integration](<https://devfeed.tech/tags/integration.md>), [messages](<https://devfeed.tech/tags/messages.md>), [messaging](<https://devfeed.tech/tags/messaging.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

This tutorial builds an appointment reminder service with Encore and Bird. It uses PostgreSQL to track reminders, a scheduled job to publish due reminders, and a pub/sub subscriber to send SMS messages and handle delivery events. It also demonstrates local end-to-end testing, including cancellation, retries, idempotency, and webhook verification.

### Source excerpt

Build messaging workflows and test backend changes end-to-end locally.

## Setting Up a Personal Assistant in Your Messaging Apps with Hermes and Upstash Box

DevFeed: [Setting Up a Personal Assistant in Your Messaging Apps with Hermes and Upstash Box](<https://devfeed.tech/articles/setting-up-a-personal-assistant-in-your-messaging-apps-with-hermes-and-upstash-box-78690.md>)

Original publisher: [Read original article](<https://upstash.com/blog/personal-assistant-in-messaging-apps-hermes-upstash-box>)

Author: Ali Tarık Şahin

Published: 2026-09-28T00:00:00Z

Content type: tutorial

Language: en

Sources: [Upstash](<https://devfeed.tech/sources/upstash.md>)

Topics: [hermes-agent](<https://devfeed.tech/topics/hermes-agent.md>), [Esp Box](<https://devfeed.tech/topics/esp-box.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>), [telegram-bot](<https://devfeed.tech/topics/telegram-bot.md>), [Slack](<https://devfeed.tech/topics/slack.md>), [Discord](<https://devfeed.tech/topics/discord.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [box](<https://devfeed.tech/tags/box.md>), [discord](<https://devfeed.tech/tags/discord.md>), [hermes](<https://devfeed.tech/tags/hermes.md>), [nous-research](<https://devfeed.tech/tags/nous-research.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [slack](<https://devfeed.tech/tags/slack.md>), [telegram](<https://devfeed.tech/tags/telegram.md>), [whatsapp](<https://devfeed.tech/tags/whatsapp.md>)

### AI overview

This tutorial shows how to run the open-source Hermes assistant on an always-on Upstash Box and connect it to WhatsApp. It covers setup, account pairing, allowlists, and restarting the gateway after a crash; other messaging platforms use a similar flow.

### Source excerpt

Hermes is an open-source agent from Nous Research that you can talk to from WhatsApp, Telegram, Slack, Discord and more. This post runs it on an Upstash Box so it stays online, then walks through connecting WhatsApp as an example. Every other messaging app follows the same flow.

## Quarkus Insights #261: Quarkus Signals -- In-Process Messaging Done Right

DevFeed: [Quarkus Insights #261: Quarkus Signals -- In-Process Messaging Done Right](<https://devfeed.tech/articles/quarkus-insights-261-quarkus-signals-in-process-messaging-done-right-64242.md>)

Original publisher: [Read original article](<https://quarkus.io/blog/quarkus-insights-261-quarkus-signals/>)

Author: James Cobb (https://twitter.com/insectengine)

Published: 2026-09-28T00:00:00Z

Content type: article

Language: en

Sources: [Quarkus - Supersonic Subatomic Java](<https://devfeed.tech/sources/quarkus-supersonic-subatomic-java.md>)

Topics: [Quarkus](<https://devfeed.tech/topics/quarkus.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Messaging](<https://devfeed.tech/topics/messaging.md>)

Tags: [messaging](<https://devfeed.tech/tags/messaging.md>), [quarkus](<https://devfeed.tech/tags/quarkus.md>), [release](<https://devfeed.tech/tags/release.md>), [talk](<https://devfeed.tech/tags/talk.md>)

### AI overview

Quarkus Insights episode 261 discusses Quarkus Signals, an experimental extension for loosely coupled communication between components within a single JVM. The episode compares Signals with CDI events, the Vert.x event bus, and reactive messaging, explaining its type-safe receiver matching, asynchronous behavior, three emission modes, execution model, and selective context propagation. Signals has been experimental since Quarkus 3.36, with stable status targeted for Quarkus 4.

### Source excerpt

This summary was generated using AI, reviewed by humans - watch the video for the full story. Quarkus Insights #261: Quarkus Signals -- In-Process Messaging Done Right Every non-trivial application eventually needs its components to talk to each other without calling each other directly. The problem is not new, and Quarkus already ships two well-established solutions: CDI events and the Vert.x event bus. So why introduce a third? In episode 261, Martin Kouba -- one of the original Quarkus engineers, author of the Qute templating engine, and now the lead developer on the Quarkus MCP server -- joins host Holly Cummins to answer exactly that question, with slides, a live demo, and a thorough Q&A. Quarkus News Holly opened with a brief news round: work on Quarkus 4 is continuing on schedule -- the release plan is tracked on the Quarkus wiki. Quarkus 3.40 is imminent: the core release is out and the platform release was being cut that week. It is the last LTS on the 3.x branch, and it should start appearing in Dependabot and Renovate update proposals shortly. Holly also took a moment to credit Martin for the Quarkus website itself: quarkus.io now runs on the Qute templating engine that Martin built, which means that bugs in Qute get discovered -- and reported directly to Martin -- by the website team. "Eating our own dog food" was the polite framing. The Problem: Three Solutions Looking for a Unified API Martin's framing is simple: Quarkus applications running in a single JVM sometimes need loosely coupled in-process communication -- where one component announces something without knowing which other components are listening, and without invoking them directly. This is distinct from distributed messaging; no brokers, no clustering, no cross-process serialization. The scope is one application, one JVM. Three existing tools already address this: CDI events -- type-safe, declarative, well-specified. Fires synchronously on the calling thread by default; all matching observers execut

[Next page](<https://devfeed.tech/topics/messaging.md?cursor=WyIyMDI2LTA5LTI4VDAwOjAwOjAwKzAwOjAwIiwgIjNlODg0NjU2LTM5ZDUtNDkyNi04YmFkLWU1Mjg1NjlkYWI1OSJd>)