# Publish-subscribe pattern

The publish-subscribe pattern (short: pubsub) is an event handling and messaging pattern where the consumer subscribes to the provider, which in return can then publish a message that can be picked up and processed by each subscribed consumer.

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

## Top 13 Microservices Interview Questions Answered

DevFeed: [Top 13 Microservices Interview Questions Answered](<https://devfeed.tech/articles/top-13-microservices-interview-questions-answered-146768.md>)

Original publisher: [Read original article](<https://newsletter.systemdesign.one/p/microservices-interview-questions>)

Author: Neo Kim

Published: 2026-11-20T12:02:22Z

Content type: article

Language: en

Sources: [System Design Newsletter](<https://devfeed.tech/sources/system-design-newsletter.md>)

Topics: [Microservices](<https://devfeed.tech/topics/microservices.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [observability](<https://devfeed.tech/topics/observability.md>), [service-mesh](<https://devfeed.tech/topics/service-mesh.md>), [modular-monolith](<https://devfeed.tech/topics/modular-monolith.md>), [monolithic-architecture](<https://devfeed.tech/topics/monolithic-architecture.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [interview](<https://devfeed.tech/tags/interview.md>), [interview-questions](<https://devfeed.tech/tags/interview-questions.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [questions](<https://devfeed.tech/tags/questions.md>), [top](<https://devfeed.tech/tags/top.md>)

### AI overview

The article presents 13 microservices interview questions and stresses weighing operational costs against benefits. Microservices enable independent releases and scaling, but introduce network failures, distributed data, and tooling needs; for a small team or new product, it recommends starting with a modular monolith and extracting services when concrete pressures emerge. It explains boundaries based on business capabilities and bounded contexts, service-owned data with APIs or event-fed copies, and sagas with compensating actions for workflows spanning services. Other guidance distinguishes API gateways from load balancers and service meshes, client-side from server-side discovery, and SOA from microservices. It also covers circuit breakers, distributed tracing, shared rate-limit counters across gateway instances, and REST conventions such as idempotency keys for retried order requests.

### Source excerpt

#205: Ace Software Engineering Job Interviews

## What to get right before you ship webhooks

DevFeed: [What to get right before you ship webhooks](<https://devfeed.tech/articles/what-to-get-right-before-you-ship-webhooks-145864.md>)

Original publisher: [Read original article](<https://www.sitepoint.com/webhooks-best-practices-before-you-ship/>)

Author: SitePoint Sponsors

Published: 2026-11-20T07:35:47Z

Content type: tutorial

Language: en

Sources: [SitePoint](<https://devfeed.tech/sources/sitepoint.md>)

Topics: [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [event-sourcing](<https://devfeed.tech/topics/event-sourcing.md>), [Cryptography](<https://devfeed.tech/topics/cryptography.md>), [API Logging](<https://devfeed.tech/topics/api-logging.md>), [Documentation](<https://devfeed.tech/topics/documentation.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-apis](<https://devfeed.tech/tags/ai-apis.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [code](<https://devfeed.tech/tags/code.md>), [deduplication](<https://devfeed.tech/tags/deduplication.md>), [delivery](<https://devfeed.tech/tags/delivery.md>), [developer-tools](<https://devfeed.tech/tags/developer-tools.md>), [event](<https://devfeed.tech/tags/event.md>), [js](<https://devfeed.tech/tags/js.md>), [log](<https://devfeed.tech/tags/log.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [retries](<https://devfeed.tech/tags/retries.md>), [standard](<https://devfeed.tech/tags/standard.md>), [webhooks](<https://devfeed.tech/tags/webhooks.md>)

### AI overview

Webhooks remove the delay and request load of polling for long-running jobs, but reliable delivery needs durable event storage and clear receiver-facing behavior. The excerpt recommends writing each event to an append-only, per-customer log in the same transaction as the state change, then exposing it through a cursor-based pull endpoint with documented retention. Use a stable event format and IDs, signed raw payloads with per-endpoint secrets, backoff retries stored across restarts, and receiver deduplication; webhook delivery can still be duplicated or arrive out of order. It also calls for per-endpoint limits, blocking private-network destinations and redirects, and customer-visible delivery attempts and replay tools. Teams can build delivery themselves or keep the event log and relay rows to Svix, which handles signing, retries, endpoint disabling, and a customer portal. The excerpt includes adaptable Node.js examples and cites Standard Webhooks verification libraries.

### Source excerpt

Before you ship webhooks: an event log, signed payloads, retries with backoff, deduplication and delivery logs, with working Node.js code and Standard Webhooks. Continue reading What to get right before you ship webhooks on SitePoint.

## RyBench: Runtime Verification Benchmarking Framework over Publish/Subscribe Networks

DevFeed: [RyBench: Runtime Verification Benchmarking Framework over Publish/Subscribe Networks](<https://devfeed.tech/articles/rybench-runtime-verification-benchmarking-framework-over-publish-subscribe-networks-139604.md>)

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

Author: Mehmet Hilmi D\\"undar (Bo\\u{g}azi\\c{c}i University), Do\\u{g}an Ulus (Bo\\u{g}azi\\c{c}i University)

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

Content type: article

Language: en

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

Topics: [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Formal verification](<https://devfeed.tech/topics/formal-verification.md>), [Phoronix Test Suite](<https://devfeed.tech/topics/phoronix-test-suite.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [also](<https://devfeed.tech/tags/also.md>), [application](<https://devfeed.tech/tags/application.md>), [arxiv](<https://devfeed.tech/tags/arxiv.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [autonomous-systems](<https://devfeed.tech/tags/autonomous-systems.md>), [based](<https://devfeed.tech/tags/based.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [benchmarking](<https://devfeed.tech/tags/benchmarking.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [channel](<https://devfeed.tech/tags/channel.md>), [components](<https://devfeed.tech/tags/components.md>), [cs-lo](<https://devfeed.tech/tags/cs-lo.md>), [cs-pf](<https://devfeed.tech/tags/cs-pf.md>), [cs-se](<https://devfeed.tech/tags/cs-se.md>), [data](<https://devfeed.tech/tags/data.md>), [distributed](<https://devfeed.tech/tags/distributed.md>), [efficiently](<https://devfeed.tech/tags/efficiently.md>), [framework](<https://devfeed.tech/tags/framework.md>), [networks](<https://devfeed.tech/tags/networks.md>), [over](<https://devfeed.tech/tags/over.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [verification](<https://devfeed.tech/tags/verification.md>)

### AI overview

RyBench provides a common way to benchmark runtime verification tools over publish/subscribe networks by publishing synthetic events in place of a monitored system. It separates event generation, serialization, and transport, allowing different strategies, formats, and transport layers to be combined. The paper evaluates throughput across configurations using Open Simulation Interface (OSI) schemas and Timescales properties, and demonstrates an end-to-end workflow with Reelay and an integration with MonPoly. The supplied abstract identifies throughput and verdict latency as practical concerns but gives no comparative latency results.

### Source excerpt

arXiv:2611.22401v1 Announce Type: cross Abstract: Autonomous systems built as distributed, node-based systems communicate via publish/subscribe middleware. Runtime Verification (RV) tools are used to monitor those systems against formal specifications, receiving monitored events through the pub/sub channel. An RV tool's practical value depends on its monitoring throughput capacity and verdict latency, besides its correctness, so a systematic benchmarking setup is needed to evaluate how efficiently these tools run. This paper presents RyBench, a pub/sub-based benchmarking framework that acts as a synthetic event publisher in place of a monitored system, providing a common benchmarking setup. RyBench separates benchmark generation, serialization, and transport into distinct components, enabling the combination of different event-generation strategies, data formats, and transport layers. We also evaluate the framework's throughput capacity across these configurations using Open Simulation Interface (OSI) schemas and Timescales properties, and illustrate the end-to-end benchmarking flow through an application to Reelay and an integration with MonPoly.

## Kafka Listeners, Mail and Live Streams in Your Backend, With Records as Entities

DevFeed: [Kafka Listeners, Mail and Live Streams in Your Backend, With Records as Entities](<https://devfeed.tech/articles/kafka-listeners-mail-and-live-streams-in-your-backend-with-records-as-entities-135299.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/kafka-mail-and-records-in-your-java-backend/>)

Author: Shai Almog

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

Content type: release

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [Apache Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [email](<https://devfeed.tech/topics/email.md>), [RabbitMQ](<https://devfeed.tech/topics/rabbitmq.md>), [jpa](<https://devfeed.tech/topics/jpa.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [accessors](<https://devfeed.tech/tags/accessors.md>), [amazon-ses](<https://devfeed.tech/tags/amazon-ses.md>), [amqp](<https://devfeed.tech/tags/amqp.md>), [annotations](<https://devfeed.tech/tags/annotations.md>), [api](<https://devfeed.tech/tags/api.md>), [backend](<https://devfeed.tech/tags/backend.md>), [events](<https://devfeed.tech/tags/events.md>), [java](<https://devfeed.tech/tags/java.md>), [jpa](<https://devfeed.tech/tags/jpa.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [live](<https://devfeed.tech/tags/live.md>), [mail](<https://devfeed.tech/tags/mail.md>), [rabbitmq](<https://devfeed.tech/tags/rabbitmq.md>), [records](<https://devfeed.tech/tags/records.md>), [redis](<https://devfeed.tech/tags/redis.md>), [server](<https://devfeed.tech/tags/server.md>), [server-sent-events](<https://devfeed.tech/tags/server-sent-events.md>), [spring](<https://devfeed.tech/tags/spring.md>), [streams](<https://devfeed.tech/tags/streams.md>)

### AI overview

The backend compiles Java to native code and generates wiring at build time, without runtime proxies or reflection. Its ORM maps immutable Java records as entities on devices and servers: saves return managed copies with generated keys and versions, while `Ref<T>` handles relationships. Record sources must use Java 17; self-referential entity records, `Map` relationships, lazy `Optional` relationships, and relationships inside embedded records are unsupported. Messaging uses Spring-style listeners across seven transports, including Kafka, RabbitMQ and Redis Streams; transactional sends go through an outbox, with at-least-once delivery, retries and dead-letter destinations. Kafka currently lacks snappy, lz4 and zstd compression, transactions and SASL. Mail is staged until commit, supports SMTP, SMTPS and Amazon SES, and retries transient failures up to six times; receiving mail and DKIM signing are unsupported. Server-sent events support reconnect resumption through `lastEventId()`, and `HttpProxy` can relay event streams without buffering.

### Source excerpt

Kafka, RabbitMQ and Redis with Spring's annotations, transactional mail, server-sent events, and Java records as entities, which JPA still doesn't allow.

## A Week of Symfony #1037 (November 9-15, 2026)

DevFeed: [A Week of Symfony #1037 (November 9-15, 2026)](<https://devfeed.tech/articles/a-week-of-symfony-1037-november-9-15-2026-134387.md>)

Original publisher: [Read original article](<https://symfony.com/blog/a-week-of-symfony-1037-november-9-15-2026>)

Author: Javier Eguiluz

Published: 2026-11-15T08:16:00Z

Content type: news

Language: en

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

Topics: [Symfony](<https://devfeed.tech/topics/symfony.md>), [project release](<https://devfeed.tech/topics/project-release.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [articles](<https://devfeed.tech/tags/articles.md>), [backend](<https://devfeed.tech/tags/backend.md>), [beta](<https://devfeed.tech/tags/beta.md>), [code](<https://devfeed.tech/tags/code.md>), [features](<https://devfeed.tech/tags/features.md>), [form](<https://devfeed.tech/tags/form.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [messenger](<https://devfeed.tech/tags/messenger.md>), [release](<https://devfeed.tech/tags/release.md>), [symfony](<https://devfeed.tech/tags/symfony.md>)

### AI overview

Symfony published the second beta of Symfony 8.2 for testing, alongside articles on its features, and announced the Symfony AI & MCP Hackathon drew around 50 teams. SymfonyLive Paris 2027 is scheduled for March 26-27 at Espace 42, with more SymfonyCon Warsaw 2026 talks announced. The project merged 197 pull requests and closed 38 issues this week. The listed changes include fixes across routing, security, locking, rate limiting, Messenger, HTTP clients, caching, and other components, as well as AI-related additions such as configurable MCP request body limits and improved agent tool handling. This overview reflects the supplied excerpt and selected change list.

### Source excerpt

This week, we published the second beta of Symfony 8.2 so you can keep testing it before its final release. Meanwhile, we kept publishing articles about Symfony 8.2 features, such as Messenger flows, AssetMapper improvements, form improvements, validator...

## Don't Just Create a Flow. Know Where to Create It.

DevFeed: [Don't Just Create a Flow. Know Where to Create It.](<https://devfeed.tech/articles/don-t-just-create-a-flow-know-where-to-create-it-134270.md>)

Original publisher: [Read original article](<https://proandroiddev.com/dont-just-create-a-flow-know-where-to-create-it-8184bd4cb6eb?source=rss----c72404660798---4>)

Author: chanzmao

Published: 2026-11-14T14:18:24Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [coroutines-flow](<https://devfeed.tech/topics/coroutines-flow.md>), [Dependency Inversion](<https://devfeed.tech/topics/dependency-inversion.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [api](<https://devfeed.tech/tags/api.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [asynchronous](<https://devfeed.tech/tags/asynchronous.md>), [callback](<https://devfeed.tech/tags/callback.md>), [database](<https://devfeed.tech/tags/database.md>), [flow](<https://devfeed.tech/tags/flow.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [mobile-app-development](<https://devfeed.tech/tags/mobile-app-development.md>), [repository](<https://devfeed.tech/tags/repository.md>), [room](<https://devfeed.tech/tags/room.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [source](<https://devfeed.tech/tags/source.md>), [suspend](<https://devfeed.tech/tags/suspend.md>), [ui](<https://devfeed.tech/tags/ui.md>)

### AI overview

Use the data source's existing Flow directly for observable Room queries and DataStore values. Bridge callback or listener APIs with `callbackFlow` in the data source, where registration and cleanup via `awaitClose` belong. Keep one-time suspend operations as suspend functions unless a stream is actually needed; collecting a Flow wrapper would rerun the operation on each collection. Repositories can map, combine, or switch among existing streams, while ViewModels derive UI state and use `stateIn()` to expose it as `StateFlow`. The article's guiding division is to convert at the source, transform in the Repository, and derive UI state in the ViewModel; it presents this as a typical approach, not a rule that every operation must use Flow.

### Source excerpt

Understanding the Architectural Timing of Flow Conversion in Kotlin and Android. Image created by AI Kotlin Flow makes it easy to work with asynchronous data streams. We can use it to observe database changes, listen for network updates, combine multiple data sources, and expose reactive data to the UI. But there is a design question that often gets overlooked: Where should we actually convert data into Flow? It's easy to wrap an API in flow {}or callbackFlow and call it a day. But doing so in the wrong layer can make an architecture unnecessarily complicated. We may end up moving callback management into the Repository, wrapping one-time operations in streams, or creating Flow objects that serve no real purpose. A better approach is to introduce Flow close to the source of the data, then let higher layers work with that stream. Let's look at what this means in practice. Start with the Data Source Different data sources expose data in different ways. Some provide callbacks, others return values through suspend functions, and some already support Flow. The first step is to understand how the underlying API delivers data. Database: Use Flow Directly Room already supports observable queries. @Query("SELECT * FROM items") fun observeItems(): Flow<List<ItemEntity>> We don't need to create another Flow around this query. Room already handles change observation and emits updated results when the underlying data changes. The same principle applies to DataStore: val showAds: Flow<Boolean> = dataStore.data.map { preferences -> preferences[SHOW_ADS] ?: true } The data source already provides a stream of changes. We should use it directly rather than introducing another abstraction. Callback APIs: Use callbackFlow Android APIs often rely on callbacks or listeners to report changes. For example, consider a location API that delivers updates through a listener. fun observeLocation(): Flow<Location> = callbackFlow { val listener = LocationListener { location -> trySend(location) }

## 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.

## Shopify Was Wrong and Right to Dump React Native

DevFeed: [Shopify Was Wrong and Right to Dump React Native](<https://devfeed.tech/articles/shopify-was-wrong-and-right-to-dump-react-native-133937.md>)

Original publisher: [Read original article](<https://www.codenameone.com/blog/shopify-was-wrong-and-right-to-dump-react-native/>)

Author: Shai Almog

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

Content type: opinion

Language: en

Sources: [CodeName One](<https://devfeed.tech/sources/codename-one.md>)

Topics: [React Native](<https://devfeed.tech/topics/react-native.md>), [Shopify](<https://devfeed.tech/topics/shopify.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [reliable codebases](<https://devfeed.tech/topics/reliable-codebases.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Cloud & Application Security](<https://devfeed.tech/topics/cloud-application-security.md>), [.NET MAUI](<https://devfeed.tech/topics/net-maui.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon](<https://devfeed.tech/tags/amazon.md>), [amazon-fire](<https://devfeed.tech/tags/amazon-fire.md>), [amazon-tablet](<https://devfeed.tech/tags/amazon-tablet.md>), [android](<https://devfeed.tech/tags/android.md>), [android-tablets](<https://devfeed.tech/tags/android-tablets.md>), [api](<https://devfeed.tech/tags/api.md>), [churn](<https://devfeed.tech/tags/churn.md>), [code](<https://devfeed.tech/tags/code.md>), [cost](<https://devfeed.tech/tags/cost.md>), [native](<https://devfeed.tech/tags/native.md>), [net-maui](<https://devfeed.tech/tags/net-maui.md>), [platforms](<https://devfeed.tech/tags/platforms.md>), [react](<https://devfeed.tech/tags/react.md>), [react-native](<https://devfeed.tech/tags/react-native.md>), [replacement](<https://devfeed.tech/tags/replacement.md>), [shopify](<https://devfeed.tech/tags/shopify.md>), [store](<https://devfeed.tech/tags/store.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

The article argues that Shopify was right to leave React Native but wrong to replace it with separate Swift and Kotlin apps: writing code is cheap, while testing, platform differences, and changing store requirements remain costly, and two codebases multiply that work. It attributes React Native's problems to its heavyweight UI model, where OS-owned widgets introduce bridges and device-specific behavior. It favors lightweight toolkits that render consistently across targets while allowing native components where needed, and notes that accessibility must be implemented by the toolkit. As supporting evidence, it cites reported post-rewrite gains in Shopify's cold start and crash-free sessions, plus examples of device-specific bugs and store changes handled by a framework. These are the article's claims; the excerpt does not independently validate them.

### Source excerpt

React Native deserved to be dumped. Two native codebases is the wrong replacement: code was never the cost. Platforms, testing and store churn are, and AI makes each of them worse.

## How Zillow runs 100 million daily notifications on AWS Step Functions

DevFeed: [How Zillow runs 100 million daily notifications on AWS Step Functions](<https://devfeed.tech/articles/how-zillow-runs-100-million-daily-notifications-on-aws-step-functions-129629.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/architecture/how-zillow-runs-100-million-daily-notifications-on-aws-step-functions/>)

Author: Nishita Kheur

Published: 2026-11-11T23:25:00Z

Content type: article

Language: en

Sources: [AWS Architecture Blog](<https://devfeed.tech/sources/aws-architecture-blog.md>)

Topics: [AWS Step Functions](<https://devfeed.tech/topics/aws-step-functions.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [notifications](<https://devfeed.tech/topics/notifications.md>), [Push Notifications](<https://devfeed.tech/topics/push-notifications.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [a-b-testing](<https://devfeed.tech/tags/a-b-testing.md>), [agent-toolkit](<https://devfeed.tech/tags/agent-toolkit.md>), [ai](<https://devfeed.tech/tags/ai.md>), [amazon-cloudwatch](<https://devfeed.tech/tags/amazon-cloudwatch.md>), [amazon-eventbridge](<https://devfeed.tech/tags/amazon-eventbridge.md>), [amazon-sqs](<https://devfeed.tech/tags/amazon-sqs.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [aws-step-functions](<https://devfeed.tech/tags/aws-step-functions.md>), [batching](<https://devfeed.tech/tags/batching.md>), [campaign](<https://devfeed.tech/tags/campaign.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [content](<https://devfeed.tech/tags/content.md>), [customer-solutions](<https://devfeed.tech/tags/customer-solutions.md>), [express](<https://devfeed.tech/tags/express.md>), [modules](<https://devfeed.tech/tags/modules.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [orchestration](<https://devfeed.tech/tags/orchestration.md>), [platform](<https://devfeed.tech/tags/platform.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Zillow replaced more than 10 campaign-specific generators with a configuration-driven Campaign Orchestrator, where each notification runs as a short-lived AWS Step Functions Express workflow and calls reusable, schema-driven Universal Content Generator modules. An in-house router handles queueing, batching, idempotency, replay, pacing, and campaign controls; separate queues and state machines isolate campaign failures. Zillow chose Express for high-volume, seconds-long, idempotent workflows, after evaluating other engines, and reports internal estimates of 9 development weeks versus 32 for a comparable in-house engine, with maintenance falling from about 8 hours weekly to 2. Batching reduces executions and module requests, but requires every step to support bulk inputs and outputs; tracking IDs preserve per-message delivery, retry, or drop decisions. The team also planned quota increases, validated JSONata through Step Functions TestState in CI, and uses schema checks for human and AI-drafted configurations.

### Source excerpt

Zillow sends more than 100 million personalized notifications a day, each as a short-lived AWS Step Functions Express workflow. See how the Comms Experience team replaced more than 10 campaign generators with one configuration-driven orchestration platform and a library of reusable content modules.

## How we moved our frontend off Firestore and built Lovable Realtime

DevFeed: [How we moved our frontend off Firestore and built Lovable Realtime](<https://devfeed.tech/articles/how-we-moved-our-frontend-off-firestore-and-built-lovable-realtime-126536.md>)

Original publisher: [Read original article](<https://lovable.dev/blog/lovable-realtime-service>)

Author: Ata Marzban

Published: 2026-11-10T11:30:00Z

Content type: article

Language: en

Sources: [Lovable](<https://devfeed.tech/sources/lovable.md>)

Topics: [Frontend & real-time](<https://devfeed.tech/topics/frontend-real-time.md>), [Firestore](<https://devfeed.tech/topics/firestore.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Full Stack Development](<https://devfeed.tech/topics/full-stack-development.md>), [build vs buy database solutions](<https://devfeed.tech/topics/build-vs-buy-database-solutions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [api](<https://devfeed.tech/tags/api.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [collaboration](<https://devfeed.tech/tags/collaboration.md>), [firestore](<https://devfeed.tech/tags/firestore.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [go](<https://devfeed.tech/tags/go.md>), [lovable](<https://devfeed.tech/tags/lovable.md>), [reactive](<https://devfeed.tech/tags/reactive.md>), [realtime](<https://devfeed.tech/tags/realtime.md>), [server](<https://devfeed.tech/tags/server.md>), [service](<https://devfeed.tech/tags/service.md>), [subscriptions](<https://devfeed.tech/tags/subscriptions.md>), [technical-blog](<https://devfeed.tech/tags/technical-blog.md>)

### AI overview

Lovable replaced browser-side Firestore listeners with a Go WebSocket service that computes each user's authorized data view and refreshes it when source data or permissions change. Firestore and Spanner updates flow through change data capture and NATS to affected subscriptions; server-side projections, hashing, and wire-level deltas reduce redundant payloads. This kept the existing databases while centralizing authorization and payload shaping in the Go backend. The team tested with shadow traffic, then rolled out by feature flag over about a week without user-facing incidents. For Sep. 5-Oct. 5, 2026, it reported a peak of 2.06 million concurrent subscriptions and 2.61 billion frames. Estimated application payload fell from a 40 TB full-snapshot baseline to 1.11 TB through deduplication, deltas, and reconnect state reuse; protocol and transport overhead were excluded. The article notes that permission dependencies require explicit field comparisons, supported by static analysis, and that long-lived WebSockets require connection-aware scaling and careful reconnect management.

### Source excerpt

How we replaced frontend Firestore listeners with a Go and NATS realtime service, with reactive authorization, server-shaped payloads, and 2.06 million live subscriptions.

## I tried Expo's new Exact with Convex

DevFeed: [I tried Expo's new Exact with Convex](<https://devfeed.tech/articles/i-tried-expo-s-new-exact-with-convex-126562.md>)

Original publisher: [Read original article](<https://stack.convex.dev/expo-exact-with-convex>)

Author: Stack

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

Content type: opinion

Language: en

Sources: [Stack](<https://devfeed.tech/sources/stack.md>)

Topics: [Expo](<https://devfeed.tech/topics/expo.md>), [Web app](<https://devfeed.tech/topics/webapp.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Python](<https://devfeed.tech/topics/python.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [chat](<https://devfeed.tech/tags/chat.md>), [client](<https://devfeed.tech/tags/client.md>), [clients](<https://devfeed.tech/tags/clients.md>), [convex](<https://devfeed.tech/tags/convex.md>), [framework](<https://devfeed.tech/tags/framework.md>), [live](<https://devfeed.tech/tags/live.md>), [mac](<https://devfeed.tech/tags/mac.md>), [phone](<https://devfeed.tech/tags/phone.md>), [reactivity](<https://devfeed.tech/tags/reactivity.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

The author ran one Exact/Contract chat UI on the web, iPhone, and Mac, with all devices receiving live updates from one Convex deployment. Because Exact cannot run npm packages at runtime, lacks a global WebSocket, and rejects timers started while handling socket messages, the standard Convex client could not be used. An agent instead built an approximately 170-line client using Exact's WebSocket and Convex's sync protocol to subscribe to queries and send mutations. That protocol is undocumented and the client is pinned to a tested Convex version, so this is an experiment rather than official Convex support. Exact is described as pre-alpha; its clock control for animation checks and rapid code updates across devices are noted as promising features.

### Source excerpt

Expo just put out Exact, a pre-alpha framework where you write your UI once in a typed language called Contract and it runs natively on your phone, your Mac and the web. I had my agent wire Convex into it to see if it would work, and it does, with a little chat app running live on all three off one Convex deployment.

## Eventually Consistent: How Do We Know the Systems Eventually Agree?

DevFeed: [Eventually Consistent: How Do We Know the Systems Eventually Agree?](<https://devfeed.tech/articles/eventually-consistent-how-do-we-know-the-systems-eventually-agree-124946.md>)

Original publisher: [Read original article](<https://devblog.kogan.com/blog/eventually-consistent-how-do-we-know-the-systems-eventually-agree>)

Author: Victor Wenas

Published: 2026-11-09T22:10:23Z

Content type: article

Language: en

Sources: [Kogan.com](<https://devfeed.tech/sources/kogan-com.md>)

Topics: [consistency](<https://devfeed.tech/topics/consistency.md>), [observability](<https://devfeed.tech/topics/observability.md>), [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Amazon EventBridge](<https://devfeed.tech/topics/amazon-eventbridge.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>)

Tags: [data-ownership](<https://devfeed.tech/tags/data-ownership.md>), [event-driven-systems](<https://devfeed.tech/tags/event-driven-systems.md>), [eventual-consistency](<https://devfeed.tech/tags/eventual-consistency.md>), [job](<https://devfeed.tech/tags/job.md>), [reconciliation](<https://devfeed.tech/tags/reconciliation.md>)

### AI overview

Event driven systems need reconciliation to detect work that stops progressing, including cases hidden by lost events. Set an evidence based deadline for expected transitions and define exceptions such as held, cancelled, or preorder orders. Start checks from the authoritative list of work that should have advanced, then ask the service that owns each fact before deciding whether to retry, record, or escalate. Make repairs through the owning service with the original idempotency key, recheck current state before acting, and track open cases until resolved. The excerpt describes using a PostgreSQL partial index to keep overdue-order queries efficient, and suggests replicas only when delayed detection is acceptable, with state confirmed before repair. Track overdue counts, oldest case age, human escalations, and whether reconciliation ran; replaying events is safe only for consumers that handle repeats.

### Source excerpt

Event-driven systems only agree eventually. Here's how we check they actually got there: deadlines, data ownership, and a reconciliation job that walks the floor.

## Find Your Stage on the Way to JavaScript Architect

DevFeed: [Find Your Stage on the Way to JavaScript Architect](<https://devfeed.tech/articles/find-your-stage-on-the-way-to-javascript-architect-122184.md>)

Original publisher: [Read original article](<https://thetshaped.dev/p/find-your-stage-on-the-way-to-javascript>)

Author: Petar Ivanov

Published: 2026-11-07T14:30:57Z

Content type: tutorial

Language: en

Sources: [The T-Shaped Dev](<https://devfeed.tech/sources/the-t-shaped-dev.md>)

Topics: [roadmaps](<https://devfeed.tech/topics/roadmaps.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [architect](<https://devfeed.tech/tags/architect.md>), [free](<https://devfeed.tech/tags/free.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [plan](<https://devfeed.tech/tags/plan.md>), [roadmap](<https://devfeed.tech/tags/roadmap.md>)

### AI overview

The roadmap's practical takeaway is to identify the first stage with an unchecked skill, then complete that stage's work project before moving on. Its six ordered stages progress from JavaScript fundamentals and maintainable code to application and database design, distributed systems, and architecture decisions spanning teams. The 20-item self-check asks whether you can perform and explain each skill today without looking it up; the author estimates two to four months per stage with five focused hours weekly, depending on work experience. The excerpt gives a Stage 4 exercise: use `pg_stat_statements` or a provider's query insights to inspect the three queries with the most total time, read their plans, improve one with an index or rewrite, and record before-and-after numbers. The full roadmap is described as a free seven-page PDF, delivered after email signup, which also subscribes the reader to the author's email list.

### Source excerpt

A 20-box self-check across six stages, and a free 7-page roadmap with the plan for each one.

## How to handle SAML certificate expiration with WorkOS webhooks

DevFeed: [How to handle SAML certificate expiration with WorkOS webhooks](<https://devfeed.tech/articles/how-to-handle-saml-certificate-expiration-with-workos-webhooks-122040.md>)

Original publisher: [Read original article](<https://workos.com/blog/saml-certificate-expiration-webhooks>)

Author: WorkOS

Published: 2026-11-06T14:45:31Z

Content type: tutorial

Language: en

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

Topics: [saml](<https://devfeed.tech/topics/saml.md>), [certificates](<https://devfeed.tech/topics/certificates.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>)

Tags: [certificate](<https://devfeed.tech/tags/certificate.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [saml](<https://devfeed.tech/tags/saml.md>), [webhooks](<https://devfeed.tech/tags/webhooks.md>), [workos](<https://devfeed.tech/tags/workos.md>)

### AI overview

WorkOS's SAML certificate events can drive one idempotent open reminder per connection, certificate type, and expiry date. Repeated or duplicate renewal notices update that reminder; route by `certificate_type`: `ResponseSigning` needs customer IT to replace the IdP certificate, while `RequestSigning` needs confirmation that the customer's IdP will pick up WorkOS's SP metadata rotation. Treat `connection.saml_certificate_renewed` as a prompt to inspect certificates for the connection, not proof the reminder can close; rotations for request signing may be silent. Escalate when `is_expired` is true. WorkOS IT contacts can receive renewal alerts and a task-scoped Admin Portal link, which expires after five minutes. Verify webhook signatures, acknowledge quickly and process asynchronously, and subscribe only to needed event types.

### Source excerpt

WorkOS sends an event before a SAML certificate expires. Turn it into one open reminder per certificate, routed to the person who can actually renew it.

## 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.

## Composable Parts Architecture

DevFeed: [Composable Parts Architecture](<https://devfeed.tech/articles/composable-parts-architecture-121430.md>)

Original publisher: [Read original article](<https://blog.devops.dev/composable-parts-architecture-b660caf40e8f?source=rss----33f8b2d9a328---4>)

Author: Scaibu

Published: 2026-11-06T09:47:16Z

Content type: article

Language: en

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

Topics: [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [architecture-components](<https://devfeed.tech/topics/architecture-components.md>), [Dependency Inversion](<https://devfeed.tech/topics/dependency-inversion.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [adapter pattern](<https://devfeed.tech/topics/adapter-pattern.md>), [Transactions](<https://devfeed.tech/topics/transactions.md>), [Functional programming](<https://devfeed.tech/topics/functional-programming.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Integration testing](<https://devfeed.tech/topics/integration-testing.md>), [event-sourcing](<https://devfeed.tech/topics/event-sourcing.md>), [Deployment Strategies](<https://devfeed.tech/topics/deployment-strategies.md>), [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [clean-architecture](<https://devfeed.tech/tags/clean-architecture.md>), [code](<https://devfeed.tech/tags/code.md>), [components](<https://devfeed.tech/tags/components.md>), [connect](<https://devfeed.tech/tags/connect.md>), [contracts](<https://devfeed.tech/tags/contracts.md>), [crash](<https://devfeed.tech/tags/crash.md>), [data](<https://devfeed.tech/tags/data.md>), [data-ownership](<https://devfeed.tech/tags/data-ownership.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [design](<https://devfeed.tech/tags/design.md>), [durability](<https://devfeed.tech/tags/durability.md>), [enterprise-architecture](<https://devfeed.tech/tags/enterprise-architecture.md>), [event](<https://devfeed.tech/tags/event.md>), [event-driven-architecture](<https://devfeed.tech/tags/event-driven-architecture.md>), [execution](<https://devfeed.tech/tags/execution.md>), [features](<https://devfeed.tech/tags/features.md>), [independent](<https://devfeed.tech/tags/independent.md>), [integrate](<https://devfeed.tech/tags/integrate.md>), [internals](<https://devfeed.tech/tags/internals.md>), [logic](<https://devfeed.tech/tags/logic.md>), [messages](<https://devfeed.tech/tags/messages.md>), [parts](<https://devfeed.tech/tags/parts.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>)

### AI overview

The architecture aims to let parts change independently by having them depend on published, versioned contracts rather than one another's internals. Each part owns its data and exposes pure logic through ports and replaceable adapters; manifests let the platform validate and wire parts without hand-edited central registries. Events through a durable log are the default connection, while synchronous requests are reserved for cases needing an immediate answer and constrained to short call chains. An atomic outbox, idempotency keys, deduplication, checkpoints, deadlines, and retries make interruptions and duplicate delivery recoverable; consumers keep read-only data copies and reconcile them against their owner. The same contracts and host protocol support different runtimes, with adapters and test kits handling host-specific integration. The excerpt also describes contract versioning, graph validation, and domain-based deployment packing as ways to manage growth. These are architectural prescriptions; the supplied text does not establish implementation results.

### Source excerpt

How small, independent parts connect, share data, survive disconnects, integrate with any host, and grow to 1000+ features -- where adding or changing something touches one place, not a hundred.Contents The six rules Vocabulary The system at a glance Anatomy of a part Contracts Connecting parts Execution model inside a part Data ownership and sharing Integrating with any system Durability: connections that break safely Changing the system Scaling to 1000+ parts Platform components Enforcement Testing Adding a new part: checklist Anti-patterns Open decisions Introduction Most large systems do not fail because a single component is badly written. They fail because components know too much about each other. One service reads another service's tables "just this once"; a handler calls three other services in sequence because it was quicker than designing an event; a central routing file collects one line from every team until nobody can change it without a merge conflict. Each shortcut is harmless on its own. Together they produce a system in which adding a field means editing a hundred files, an outage in one corner takes down everything, and a dropped network connection corrupts data. This document describes a structure that prevents those outcomes by design rather than by discipline. It rests on two ideas: No part knows another part. Parts know contracts. A part is aware of its own logic and of the published, versioned contracts it uses. It never sees another part's code, storage, or deployment details. Because nothing depends on internals, internals can change freely. Every connection is assumed to break, and breaking must cost nothing. Networks drop, processes crash, and messages arrive twice or out of order. Instead of trying to prevent these failures, the structure makes each one harmless: nothing is lost, nothing happens twice, and nothing waits forever. Everything that follows is an elaboration of those two ideas, together with the tooling that keeps them true as

## Article: Identity as an Architectural Concern: Enterprise IAM Beyond Authentication

DevFeed: [Article: Identity as an Architectural Concern: Enterprise IAM Beyond Authentication](<https://devfeed.tech/articles/article-identity-as-an-architectural-concern-enterprise-iam-beyond-authentication-120951.md>)

Original publisher: [Read original article](<https://www.infoq.com/articles/identity-as-architecture/>)

Author: Vaishnavi Khosla

Published: 2026-11-06T09:00:00Z

Content type: article

Language: en

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

Topics: [identity and access management](<https://devfeed.tech/topics/identity-and-access-management.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [rbac](<https://devfeed.tech/topics/rbac.md>), [HashiCorp Vault](<https://devfeed.tech/topics/hashicorp-vault.md>), [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [architecture-design](<https://devfeed.tech/tags/architecture-design.md>), [article](<https://devfeed.tech/tags/article.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [based](<https://devfeed.tech/tags/based.md>), [data](<https://devfeed.tech/tags/data.md>), [design](<https://devfeed.tech/tags/design.md>), [development](<https://devfeed.tech/tags/development.md>), [don-t](<https://devfeed.tech/tags/don-t.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [event](<https://devfeed.tech/tags/event.md>), [experience](<https://devfeed.tech/tags/experience.md>), [governance](<https://devfeed.tech/tags/governance.md>), [graph](<https://devfeed.tech/tags/graph.md>), [iam](<https://devfeed.tech/tags/iam.md>), [identity](<https://devfeed.tech/tags/identity.md>), [identity-as-architecture](<https://devfeed.tech/tags/identity-as-architecture.md>), [identity-management](<https://devfeed.tech/tags/identity-management.md>), [java](<https://devfeed.tech/tags/java.md>), [management](<https://devfeed.tech/tags/management.md>), [models](<https://devfeed.tech/tags/models.md>), [oauth](<https://devfeed.tech/tags/oauth.md>), [rbac](<https://devfeed.tech/tags/rbac.md>), [scope](<https://devfeed.tech/tags/scope.md>), [security](<https://devfeed.tech/tags/security.md>), [service](<https://devfeed.tech/tags/service.md>), [single-sign-on](<https://devfeed.tech/tags/single-sign-on.md>), [stream](<https://devfeed.tech/tags/stream.md>)

### AI overview

At enterprise scale, identity design shapes data models, service boundaries, ownership governance, and revocation behavior. The author describes modeling ownership and time-bounded access as relationships in Neo4j, queried through GraphQL; this made common ownership and validity questions direct, though it adds datastore and modeling costs, and the article says flat RBAC remains suitable for small, single-app setups. A unified workflow for attestation, credential rotation, and vaulting reduced reported revocation time from about three days to under one. Because the vault is owned by another team, the integration fails closed and reconciles its state before marking vaulting complete. Across services, scoped OAuth 2.0 token exchange carries identity context while a policy decision point makes authorization decisions. Kafka distributes entitlement changes, so revocation is eventually consistent: consumers invalidate cached decisions, and a maximum cache age bounds stale access if an event is lost, at the cost of more source-of-truth checks when that limit is shorter.

### Source excerpt

The way you design your identities will drive your data models, your service scope, and your revocation policies; enterprise identity management is thus an architectural problem, not an afterthought. Based on our experience in service account governance, this article touches upon graph vs. RBAC, integrating a vault you don't own, and bounding revocation latency for an event stream. By Vaishnavi Khosla

## Add push notifications to your Android app without Firebase

DevFeed: [Add push notifications to your Android app without Firebase](<https://devfeed.tech/articles/add-push-notifications-to-your-android-app-without-firebase-121684.md>)

Original publisher: [Read original article](<https://appwrite.io/blog/post/add-push-notifications-to-your-android-app>)

Author: Atharva Deosthale

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

Content type: tutorial

Language: en

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

Topics: [Push Notifications](<https://devfeed.tech/topics/push-notifications.md>), [notifications](<https://devfeed.tech/topics/notifications.md>), [Android](<https://devfeed.tech/topics/android.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [android-13](<https://devfeed.tech/tags/android-13.md>), [android-15](<https://devfeed.tech/tags/android-15.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [app](<https://devfeed.tech/tags/app.md>), [customers](<https://devfeed.tech/tags/customers.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [notify](<https://devfeed.tech/tags/notify.md>), [open](<https://devfeed.tech/tags/open.md>), [order](<https://devfeed.tech/tags/order.md>), [push-notifications](<https://devfeed.tech/tags/push-notifications.md>), [send](<https://devfeed.tech/tags/send.md>), [tap](<https://devfeed.tech/tags/tap.md>), [tutorials](<https://devfeed.tech/tags/tutorials.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Appwrite Push lets a Kotlin Android app send notifications to a signed-in user across their devices without Firebase setup or FCM token collection. Register the Android app in Appwrite, add the Android SDK (API 24 or later), and subscribe after sign-in; an Appwrite Function can send pushes to a user ID when order status changes. Include an order ID in message data and handle taps with `getInitialNotification` and `onNotificationOpened`. Foreground messages reach the callback; background notifications can arrive after process death, reboot, or reconnect, but timing is delayed (15 seconds to two minutes in Android 15 tests). A foreground service reduced tested background delivery to within two seconds, with a quiet ongoing notification and a Google Play declaration requirement. Force-stopped apps receive nothing until reopened. Close Push before deleting a session to stop delivery for the previous user. Repeated order updates can resend notifications, so the tutorial recommends tracking the last status notified.

### Source excerpt

Send push notifications to a Kotlin app with Appwrite Push. Notify customers when an order ships, deliver while the app is closed, and open the order on tap.

## Announcing Appwrite Push: push notifications without Firebase

DevFeed: [Announcing Appwrite Push: push notifications without Firebase](<https://devfeed.tech/articles/announcing-appwrite-push-push-notifications-without-firebase-121687.md>)

Original publisher: [Read original article](<https://appwrite.io/blog/post/announcing-appwrite-push>)

Author: Arnab Chatterjee

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

Content type: release

Language: en

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

Topics: [Push Notifications](<https://devfeed.tech/topics/push-notifications.md>), [Appwrite](<https://devfeed.tech/topics/appwrite.md>), [React Native](<https://devfeed.tech/topics/react-native.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [announcements](<https://devfeed.tech/tags/announcements.md>), [api](<https://devfeed.tech/tags/api.md>), [apple](<https://devfeed.tech/tags/apple.md>), [at-least-once-delivery](<https://devfeed.tech/tags/at-least-once-delivery.md>), [background-work](<https://devfeed.tech/tags/background-work.md>), [broker](<https://devfeed.tech/tags/broker.md>), [browser](<https://devfeed.tech/tags/browser.md>), [callback](<https://devfeed.tech/tags/callback.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [console](<https://devfeed.tech/tags/console.md>), [container](<https://devfeed.tech/tags/container.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [flutter](<https://devfeed.tech/tags/flutter.md>), [ios](<https://devfeed.tech/tags/ios.md>), [notifications](<https://devfeed.tech/tags/notifications.md>), [push-notifications](<https://devfeed.tech/tags/push-notifications.md>), [react-native](<https://devfeed.tech/tags/react-native.md>), [token](<https://devfeed.tech/tags/token.md>), [web](<https://devfeed.tech/tags/web.md>)

### AI overview

Appwrite Push delivers messages through an SDK connection to Appwrite, without requiring a Firebase project, service account, or device tokens. After signing in, an app subscribes to the user's messages; servers can send to a user ID, and the SDK handles notifications and tap data. Offline messages are retained for up to seven days, with up to five per topic replayed on reconnect. Delivery differs by platform: Android reconnects on a schedule or can use a foreground service for immediate delivery; iOS uses APNs and a Notification Service Extension to reach suspended apps; web delivery requires an open tab, with missed messages replayed when it reopens. FCM and APNs can remain enabled alongside Appwrite Push; an Appwrite push target is needed for topics, iOS background delivery, or devices with other push targets. Self-hosted support starts with Appwrite 2.6.0.

### Source excerpt

Appwrite Push delivers push notifications from Appwrite straight to your Android, iOS, web, Flutter, and React Native apps, with no Firebase project, service account, or device token to manage.

## Change Data Capture in SQLite, Without the Triggers

DevFeed: [Change Data Capture in SQLite, Without the Triggers](<https://devfeed.tech/articles/change-data-capture-in-sqlite-without-the-triggers-121133.md>)

Original publisher: [Read original article](<https://turso.tech/blog/change-data-capture-in-sqlite-without-the-triggers>)

Author: Jeff Olson

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

Content type: article

Language: en

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

Topics: [Turso](<https://devfeed.tech/topics/turso.md>), [SQLite](<https://devfeed.tech/topics/sqlite.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [event-driven data processing](<https://devfeed.tech/topics/event-driven-data-processing.md>), [transaction-log](<https://devfeed.tech/topics/transaction-log.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Debezium Connector](<https://devfeed.tech/topics/debezium-connector.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [built-in](<https://devfeed.tech/tags/built-in.md>), [capture](<https://devfeed.tech/tags/capture.md>), [cdc](<https://devfeed.tech/tags/cdc.md>), [change](<https://devfeed.tech/tags/change.md>), [change-data-capture](<https://devfeed.tech/tags/change-data-capture.md>), [consumer](<https://devfeed.tech/tags/consumer.md>), [data](<https://devfeed.tech/tags/data.md>), [database](<https://devfeed.tech/tags/database.md>), [delete](<https://devfeed.tech/tags/delete.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [here](<https://devfeed.tech/tags/here.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [insert](<https://devfeed.tech/tags/insert.md>), [records](<https://devfeed.tech/tags/records.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [sqlite](<https://devfeed.tech/tags/sqlite.md>), [triggers](<https://devfeed.tech/tags/triggers.md>), [turso](<https://devfeed.tech/tags/turso.md>), [update](<https://devfeed.tech/tags/update.md>), [works](<https://devfeed.tech/tags/works.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

Turso Database adds built-in SQLite CDC that records committed inserts, updates, and deletes in `turso_cdc` without per-table triggers. Consumers can poll the ordered stream, group records by transaction, and resume from a saved watermark; they should make processing idempotent because crashes can replay already-applied changes. Modes retain primary keys, before or after images, or full details, and schema changes are recorded. The feature is actively developed: pin versions, and snapshot column lists before migrations because decoding old records with today's columns can misalign them. CDC captures row facts, not domain meaning or user identity; those require application-side context. The excerpt also cautions that retention cleanup on synced databases may remove changes Sync has not pushed.

### Source excerpt

Built-in CDC in Turso Database records every insert, update, and delete for you. Here is how it works, where it is rough, and how to write a consumer that survives restarts.

## Workflow SDK adds idempotent starts

DevFeed: [Workflow SDK adds idempotent starts](<https://devfeed.tech/articles/workflow-sdk-adds-idempotent-starts-117742.md>)

Original publisher: [Read original article](<https://vercel.com/changelog/atomic-start-hooks-in-the-workflow-sdk>)

Author: Alex Langenfeld

Published: 2026-11-04T18:55:00Z

Content type: release

Language: en

Sources: [Vercel News](<https://devfeed.tech/sources/vercel-news.md>)

Topics: [SDK](<https://devfeed.tech/topics/sdk.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>)

Tags: [atomic](<https://devfeed.tech/tags/atomic.md>), [idempotency](<https://devfeed.tech/tags/idempotency.md>), [sdk](<https://devfeed.tech/tags/sdk.md>), [workflow](<https://devfeed.tech/tags/workflow.md>)

### AI overview

Workflow SDK 5.4.0 makes `start()` admit a run and claim a hook atomically, closing the duplicate-start race in the former lookup-then-start pattern. A domain token acts as the idempotency key: one run owns it, and a duplicate start throws `HookConflictError` with the owning run's ID without creating another run. The claimed hook is available immediately; `resumeHook` can send early messages, which are buffered and delivered in order, while `createHook({ token })` inside the run binds to that hook without registering another or adding a step. The workflow may also never open the hook and still complete normally. `experimental_minRetention` keeps the token unavailable for a period counted from start, refusing late duplicates after the run ends.

### Source excerpt

The Workflow SDK's start() function can now admit a run and claim a hook in one atomic step. Duplicate workflow starts fail safely. The atomic start replaces the previous getHookByToken()-then-start() pattern, whose gap between the lookup and the start left a documented duplicate-start race. Subscribe to messages inside the run The claimed Hook exists from the moment the run is admitted, so resumeHook works even before the run begins executing, and early payloads are buffered and delivered in order. Inside the workflow, createHook({ token }) with the same token binds to the already-claimed hook: guaranteed, registering nothing new, adding no step, and resolving getConflict() to null. Idempotency with no extra code The token is the idempotency key, and it comes from your own domain: an order ID, an invoice ID, an import ID, or a request ID. The token alone guarantees idempotency. Exactly one run owns it, and a duplicate start() throws HookConflictError carrying the owner's conflictingRunId and never becomes a run. The workflow doesn't have to open the hook at all, and if it never does, the token was only an idempotency key and the run completes normally. Setting experimental_minRetention keeps the token unavailable after the run ends, counted from start(), so late duplicates are still refused. Upgrade to workflow 5.3.1 and read the idempotency documentation to get started. Read more

## Send your own AuthKit emails: Invitations, Magic Auth, verification and password reset

DevFeed: [Send your own AuthKit emails: Invitations, Magic Auth, verification and password reset](<https://devfeed.tech/articles/send-your-own-authkit-emails-invitations-magic-auth-verification-and-password-reset-117623.md>)

Original publisher: [Read original article](<https://workos.com/blog/authkit-custom-emails>)

Author: WorkOS

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

Content type: tutorial

Language: en

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

Topics: [email](<https://devfeed.tech/topics/email.md>), [password reset](<https://devfeed.tech/topics/password-reset.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [passwords](<https://devfeed.tech/topics/passwords.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [3](<https://devfeed.tech/tags/3.md>), [acceptance](<https://devfeed.tech/tags/acceptance.md>), [account](<https://devfeed.tech/tags/account.md>), [admin](<https://devfeed.tech/tags/admin.md>), [all](<https://devfeed.tech/tags/all.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [auth](<https://devfeed.tech/tags/auth.md>), [email](<https://devfeed.tech/tags/email.md>), [email-verification](<https://devfeed.tech/tags/email-verification.md>), [magic](<https://devfeed.tech/tags/magic.md>), [one](<https://devfeed.tech/tags/one.md>), [password](<https://devfeed.tech/tags/password.md>), [password-reset](<https://devfeed.tech/tags/password-reset.md>), [reset](<https://devfeed.tech/tags/reset.md>), [send](<https://devfeed.tech/tags/send.md>), [turning](<https://devfeed.tech/tags/turning.md>), [verification](<https://devfeed.tech/tags/verification.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Turning off AuthKit's default emails applies across an entire environment and leaves you responsible for invitation, Magic Auth, email verification, and password reset messages. For objects created outside your backend, subscribe to the corresponding events, retrieve each full object through its get endpoint because event payloads omit the secret, then email its address with the code or link. API-created objects return the needed values directly. Invitations require both `invitation.created` and `invitation.resent`; manually sent invitations also need event handling. Email verification remains on, and invited users who sign up with a password must verify when WorkOS did not email the invitation. Hosted AuthKit pages use default invitation and reset URLs; custom pages must capture and process the relevant token. Test in staging, account for Dashboard and hosted UI flows, and handle localization yourself. The article notes that Custom Email Providers may be a smaller option when only the sending domain or provider needs to change.

### Source excerpt

Turning off AuthKit's default emails is one setting. The work is the four flows you then own: invitations, Magic Auth, email verification and password reset.

## Stop Unnecessary React Context Re-renders

DevFeed: [Stop Unnecessary React Context Re-renders](<https://devfeed.tech/articles/stop-unnecessary-react-context-re-renders-117826.md>)

Original publisher: [Read original article](<https://jsdev.space/react-context-field/>)

Author: anton liberant

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

Content type: article

Language: en

Sources: [JavaScript Development](<https://devfeed.tech/sources/javascript-development.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [Publish-subscribe pattern](<https://devfeed.tech/topics/pubsub.md>), [Zustand](<https://devfeed.tech/topics/zustand.md>)

Tags: [context](<https://devfeed.tech/tags/context.md>), [field](<https://devfeed.tech/tags/field.md>), [radixui](<https://devfeed.tech/tags/radixui.md>), [react](<https://devfeed.tech/tags/react.md>), [react-slider](<https://devfeed.tech/tags/react-slider.md>), [slider](<https://devfeed.tech/tags/slider.md>), [stable](<https://devfeed.tech/tags/stable.md>), [subscriptions](<https://devfeed.tech/tags/subscriptions.md>), [tailwind](<https://devfeed.tech/tags/tailwind.md>)

### AI overview

React Context updates consumers when its provider value changes; it does not track which object fields each consumer reads, and React.memo does not block updates from a consumed Context. For frequently changing shared state, the article shows keeping a stable store in Context and using useSyncExternalStore to subscribe components to individual fields. The store compares old and new field values with Object.is and notifies only listeners for changed fields, while stable snapshots let React skip renders for unchanged values. The approach adds custom store and SSR snapshot requirements; server and hydration snapshots must agree, and external-store updates may require synchronous rendering instead of benefiting from transitions. Splitting state and action contexts can help writer-only components, while ordinary Context may suffice for small cases. Measure render costs before adding this complexity; for larger applications, an established library may be easier to maintain.

### Source excerpt

Learn how to prevent unnecessary React Context re-renders using stable stores, field-level subscriptions, and useSyncExternalStore.

## 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.

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