# The lex records whose category is event-messaging-async

This index as JSON: https://banes-lab.com/json/api/facets/lex/category/event-messaging-async

## Entries

- [Blocking Synchronous Chains](https://banes-lab.com/records/lex/blocking-synchronous-chains.md): Chaining services through blocking synchronous calls, so one slow link stalls the entire request.
- [CRUD-Only State Persistence](https://banes-lab.com/records/lex/crud-only-state-persistence.md): Persisting only current state via create-read-update-delete, discarding the history that event sourcing preserves.
- [Direct Event Handler Calls](https://banes-lab.com/records/lex/direct-event-handler-calls.md): Invoking event handlers by direct method call, coupling emitter to handler and defeating the event bus.
- [Direct Point-to-Point Calls](https://banes-lab.com/records/lex/direct-point-to-point-calls.md): Wiring services together with direct point-to-point calls, coupling each sender to specific receivers.
- [Duplicate Side Effects](https://banes-lab.com/records/lex/duplicate-side-effects.md): Reprocessing a message so its side effects run more than once, corrupting state when not idempotent.
- [Global ACID Transaction](https://banes-lab.com/records/lex/global-acid-transaction.md): Attempting a single ACID transaction spanning multiple distributed services, creating tight coupling and availability loss.
- [Hidden Temporal Coupling](https://banes-lab.com/records/lex/hidden-temporal-coupling.md): An undocumented ordering requirement between operations that must run in a specific sequence to work correctly.
- [In-Memory Direct Invocation](https://banes-lab.com/records/lex/in-memory-direct-invocation.md): Calling a component directly in-process where a durable queue is needed, losing buffering and delivery guarantees.
- [In-Place Mutation](https://banes-lab.com/records/lex/in-place-mutation.md): Overwriting existing records in place where an append-only log is required, destroying history.
- [Infinite Redelivery Loop](https://banes-lab.com/records/lex/infinite-redelivery-loop.md): Endlessly redelivering a failing message with no dead-letter path, blocking the queue indefinitely.
- [Infrastructure Events in Domain](https://banes-lab.com/records/lex/infrastructure-events-in-domain.md): Leaking infrastructure or technical events into the domain model, polluting it with concerns it should not hold.
- [Internal Domain Event Leakage](https://banes-lab.com/records/lex/internal-domain-event-leakage.md): Exposing internal domain events to external consumers, coupling them to private model details.
- [Irreversible Side Effects](https://banes-lab.com/records/lex/irreversible-side-effects.md): Performing side effects that cannot be undone within a workflow that may need to roll back.
- [Mutable State Only](https://banes-lab.com/records/lex/mutable-state-only.md): Keeping only mutable current state with no event record, so past states and changes cannot be recovered.
- [Point-to-Point Coupling](https://banes-lab.com/records/lex/point-to-point-coupling.md): Coupling a sender directly to a specific receiver, so adding a consumer requires changing the sender.
- [Shared Database](https://banes-lab.com/records/lex/shared-database.md): Multiple services reading and writing one shared database, coupling them and destroying service autonomy.
- [Single Serial Consumer](https://banes-lab.com/records/lex/single-serial-consumer.md): Processing a queue with one consumer in series, so throughput cannot scale with load.
- [Unified CRUD Model](https://banes-lab.com/records/lex/unified-crud-model.md): Using one shared model for both reads and writes, preventing each from being optimized for its purpose.
- [Broker/Event Bus](https://banes-lab.com/records/lex/broker-event-bus.md): A runtime intermediary that routes messages between publishers and subscribers.
- [Command/Query Separation](https://banes-lab.com/records/lex/command-query-separation.md): Separating operations that change state from those that return data, so each method has a single purpose.
- [Compensating Transactions](https://banes-lab.com/records/lex/compensating-transactions.md): Undoing a completed step's effects with an offsetting action when a later step in a distributed workflow fails.
- [Consumer](https://banes-lab.com/records/lex/consumer.md): A component that receives and processes messages from a queue or topic.
- [Deduplication Key](https://banes-lab.com/records/lex/deduplication-key.md): A stable identifier attached to a message that lets a consumer detect and drop duplicates.
- [Event Contract](https://banes-lab.com/records/lex/event-contract.md): The agreed schema and semantics of an event that publishers and subscribers both honor.
- [Event Schema](https://banes-lab.com/records/lex/event-schema.md): A formal definition of the structure and fields of an event's payload.
- [Event Semantics](https://banes-lab.com/records/lex/event-semantics.md): The agreed meaning of what an event represents and the conditions under which it is emitted.
- [Events](https://banes-lab.com/records/lex/events.md): Records of things that have happened in a system, emitted for other components to react to.
- [Immutable Events](https://banes-lab.com/records/lex/immutable-events.md): The requirement that recorded events never change once written, only be appended to.
- [Local Transaction](https://banes-lab.com/records/lex/local-transaction.md): A transaction confined to a single service's own datastore, the atomic unit a saga or outbox composes.
- [Message Queue/Topics](https://banes-lab.com/records/lex/message-queue-topics.md): The durable queues and topics through which a broker routes messages to consumers.
- [Message Relay](https://banes-lab.com/records/lex/message-relay.md): A component that reads pending messages from an outbox and publishes them to the broker.
- [Ordered Log](https://banes-lab.com/records/lex/ordered-log.md): An append-only sequence of records that preserves the order in which they were written.
- [Own Data](https://banes-lab.com/records/lex/own-data.md): The requirement that each service alone own and control its data store.
- [Publisher](https://banes-lab.com/records/lex/publisher.md): A component that emits messages to a topic or bus for subscribers to receive.
- [Reconciliation](https://banes-lab.com/records/lex/reconciliation.md): The activity of detecting and resolving divergence between replicas so they converge to a consistent state.
- [Retry](https://banes-lab.com/records/lex/retry.md): Re-attempting a failed operation, typically after a delay, to overcome a transient fault.
- [Reversible/Compensable Step](https://banes-lab.com/records/lex/reversible-compensable-step.md): The requirement that each step in a distributed workflow can be undone by a compensating action.
- [Routing](https://banes-lab.com/records/lex/routing.md): The ability to direct each message to its correct destination based on topic, key, or rule.
- [Subscriber](https://banes-lab.com/records/lex/subscriber.md): A component that registers interest in a topic and receives its messages.
- [Subscriber Model](https://banes-lab.com/records/lex/subscriber-model.md): A representation of which consumers subscribe to which topics and how they receive messages.
- [User Expectations](https://banes-lab.com/records/lex/user-expectations.md): The behavior users assume a system will exhibit, such as seeing their own writes immediately.
- [Asynchronous Processing](https://banes-lab.com/records/lex/asynchronous-processing.md): The ability to handle work without blocking the caller, decoupling request from completion.
- [Atomic State Change + Message Publish](https://banes-lab.com/records/lex/atomic-state-change-message-publish.md): The ability to commit a state change and publish its corresponding message as one atomic unit.
- [Consumer Elasticity](https://banes-lab.com/records/lex/consumer-elasticity.md): The ability to add or remove consumers dynamically to match message volume.
- [Cross-Service Communication](https://banes-lab.com/records/lex/cross-service-communication.md): The ability for independent services to exchange information without direct coupling.
- [Decoupled Domain Reactions](https://banes-lab.com/records/lex/decoupled-domain-reactions.md): The ability for domain logic to react to events without the emitter knowing its consumers.
- [Decoupled Event Distribution](https://banes-lab.com/records/lex/decoupled-event-distribution.md): The ability to distribute events to many consumers without the source depending on any of them.
- [Distributed Autonomy](https://banes-lab.com/records/lex/distributed-autonomy.md): The ability for distributed nodes to operate and decide independently without central coordination.
- [Failure Recovery](https://banes-lab.com/records/lex/failure-recovery.md): The ability to restore correct operation after a failure through compensation or retry.
- [Fan-Out Notification](https://banes-lab.com/records/lex/fan-out-notification.md): The ability to deliver one event to many interested subscribers at once.
- [Historical Reconstruction](https://banes-lab.com/records/lex/historical-reconstruction.md): The ability to rebuild past state by replaying the recorded sequence of events.
- [Long-Running Transactions](https://banes-lab.com/records/lex/long-running-transactions.md): The ability to carry a business transaction across many steps and a long duration via compensation.
- [Parallel Message Processing](https://banes-lab.com/records/lex/parallel-message-processing.md): The ability for multiple consumers to process messages from the same source at once.
- [Poison-Message Quarantine](https://banes-lab.com/records/lex/poison-message-quarantine.md): The ability to divert a repeatedly-failing message to a separate queue so it stops blocking others.
- [Read/Write Model Optimization](https://banes-lab.com/records/lex/read-write-model-optimization.md): The ability to shape read and write models independently for their differing access patterns.
- [Reprocessing After Fix](https://banes-lab.com/records/lex/reprocessing-after-fix.md): The ability to reprocess quarantined messages once the underlying defect is fixed.
- [Safe Message Redelivery](https://banes-lab.com/records/lex/safe-message-redelivery.md): The ability to redeliver a message without causing duplicate effects, given idempotent handling.
- [Temporal Modeling](https://banes-lab.com/records/lex/temporal-modeling.md): The ability to model how state evolved over time by preserving each change as an event.
- [Temporal Queries](https://banes-lab.com/records/lex/temporal-queries.md): The ability to ask what a system's state was at any past point in time.
- [Work Distribution](https://banes-lab.com/records/lex/work-distribution.md): The ability to spread units of work across many workers via a broker.
- [At-Least-Once Delivery Safety](https://banes-lab.com/records/lex/at-least-once-delivery-safety.md): The degree to which a message is guaranteed to be delivered at least once, tolerating duplicates.
- [Decoupling](https://banes-lab.com/records/lex/decoupling.md): The degree to which components depend on one another minimally, so each can change independently.
- [Event Reliability](https://banes-lab.com/records/lex/event-reliability.md): The degree to which events are guaranteed to be delivered despite failures.
- [Business Complexity](https://banes-lab.com/records/lex/business-complexity.md): The degree of domain intricacy that a coordination mechanism must accommodate.
- [Delivery Ordering](https://banes-lab.com/records/lex/delivery-ordering.md): The degree to which messages are delivered in a defined order, which broad fan-out can weaken.
- [Duplication with Domain Events](https://banes-lab.com/records/lex/duplication-with-domain-events.md): The degree of overlap between integration events and domain events that must be kept in sync.
- [Event Granularity](https://banes-lab.com/records/lex/event-granularity.md): The degree of coarseness or fineness at which events are defined, trading detail against volume.
- [Event Storm / Traceability](https://banes-lab.com/records/lex/event-storm-traceability.md): The degree to which a high volume of events makes end-to-end flows hard to trace.
- [Global Consistency](https://banes-lab.com/records/lex/global-consistency.md): The degree to which all nodes reflect the same state at once, which service autonomy gives up.
- [Immediate Consistency](https://banes-lab.com/records/lex/immediate-consistency.md): The degree to which a read reflects the latest write instantly, which asynchronous processing defers.
- [Operational Dependency](https://banes-lab.com/records/lex/operational-dependency.md): The degree to which a system's operation depends on a message broker remaining available.
- [Query Complexity](https://banes-lab.com/records/lex/query-complexity.md): The degree of difficulty of answering queries when state is stored as an event history rather than current rows.
- [Relay Complexity](https://banes-lab.com/records/lex/relay-complexity.md): The degree of added complexity of running a relay process that forwards messages from an outbox.
- [State Overhead](https://banes-lab.com/records/lex/state-overhead.md): The degree of extra state a consumer must retain to deduplicate or order messages.
- [Storage Growth](https://banes-lab.com/records/lex/storage-growth.md): The degree to which an append-only log's storage footprint grows unbounded over time.
- [Storage Volume](https://banes-lab.com/records/lex/storage-volume.md): The degree to which retaining a full event stream consumes large amounts of storage.
- [Strong Consistency](https://banes-lab.com/records/lex/strong-consistency.md): The degree to which all reads see the latest write, which event-driven asynchrony relaxes.
- [Strong Immediate Consistency](https://banes-lab.com/records/lex/strong-immediate-consistency.md): The degree to which every read reflects the most recent write without delay, which eventual consistency relaxes.
- [Workflow Complexity](https://banes-lab.com/records/lex/workflow-complexity.md): The degree of intricacy of coordinating a multi-step distributed workflow.