Event
A software event is an occurrence, state change, or notification that a system can detect, record, communicate, or handle.
Functional Programming in C#, Second Edition
An event is the example application's record of an account state transition that can be persisted and published.
- How it is used
- Uses events as persisted records of account state transitions in an event-sourced system.
- How deep it goes
- Works through event records, state transitions, command handling, and publication, while leaving infrastructure-specific atomicity mechanisms open.
- Examples
- Uses account creation, cash deposits, freezes, and debited transfers, alongside auction bids and insurance product changes.
- What you can do after
- Evaluate event sourcing for a domain and model account events and transitions in C#.
Read how Functional Programming in C#, Second Edition explains event →
Grokking Machine Learning
In Bayesian reasoning, an event is an occurrence or observation that provides information for updating a probability.
- How it is used
- Uses an event as new information for updating a probability through Bayesian reasoning.
- How deep it goes
- Defines events and illustrates their effect with medical and email examples before introducing Bayes’ theorem.
- Examples
- Uses a positive medical diagnosis, the Amazon rain forest, and the word “lottery” in spam emails.
- What you can do after
- Apply Bayesian reasoning to update a probability using an informative observation.
Grokking Software Architecture
An immutable representation of something that has happened and may be communicated to downstream consumers.
- How it is used
- Uses events to decouple services in time and let independent consumers react to past facts.
- How deep it goes
- Explains event design and broker lifecycle with retry risks, while deferring distributed transactions and idempotency in depth.
- Examples
- Uses an OrderPlaced record, a shipping-label retry, and a CommentPosted pipeline with simulated AI analysis.
- What you can do after
- Evaluate and understand when to use events, what data to include, and why consumers must account for retries.
Microservices Patterns, Second Edition
A notification representing something notable that has occurred in an application.
- How it is used
- Signals notable application or service occurrences to users and collaborating services, often as the result of an operation.
- How deep it goes
- Defines events as messages about notable occurrences, often domain-object state changes, and distinguishes them from documents, commands, and replies.
- Examples
- Uses order creation, cancellation, and delivery notifications, and describes events that keep CQRS views current.
- What you can do after
- Understand how events communicate operation outcomes, form service APIs, and provide updates for CQRS views.
Read how Microservices Patterns, Second Edition explains event →
Grokking Machine Learning, Second Edition
An event is an occurrence or observed outcome that provides information for updating a probability.
- How it is used
- Uses an observed occurrence to refine a prior probability into a posterior probability.
- How deep it goes
- Defines events and works through counting, complements, conditional probabilities, and probability trees before Bayes’ theorem.
- Examples
- Uses rain in the Amazon rainforest, a positive medical test, and the word “lottery” in spam emails.
- What you can do after
- Evaluate updated probabilities by identifying an event and comparing outcomes within the relevant subset.
Read how Grokking Machine Learning, Second Edition explains event →
Also covered in
- Event Processing in Action
- Architecture Modernization: Socio-technical alignment of software, strategy, and structure
- Web Components in Action
- React Quickly, Second Edition
- Software Design for Python Programmers
- Unit Testing Principles, Practices, and Patterns
- Kafka for Architects
- MongoDB 8.0 in Action, Third Edition
- Build a Frontend Web Framework (From Scratch)
- Kubernetes in Action, Second Edition
- Python Concurrency with asyncio
- Vanilla WebIn early access (MEAP)
What to know first
- JavaScriptJavaScript is a high-level, dynamically typed programming language standardized as ECMAScript and used for web and general-purpose programming.
- Document Object ModelThe Document Object Model is a platform-independent programming interface that represents a document as a structured tree of nodes and provides ways to access and modify its content and structure.
- JSONJSON is a language-independent text-based data-interchange format that represents structured values using objects, arrays, strings, numbers, booleans, and null.
- handlerA handler is a software routine or component invoked to process an event, request, message, or other input.
Related concepts
- commandcontrasts with · A command is an instruction or representation of a requested operation that a system can execute, often with parameters and potentially changing state.
- event processing systemproduced by · A software system that processes event representations to detect situations, produce observations, or route events.
- event sourcingused by · Event sourcing is a persistence pattern in which state changes are recorded as an ordered sequence of events from which current state can be derived or reconstructed.
- providerproduced by · A provider is a software component or system that exposes capabilities, data, or processing for use by other components or systems.
Questions about event
What is event?
A software event is an occurrence, state change, or notification that a system can detect, record, communicate, or handle.
Which Manning books explain event?
Functional Programming in C#, Second Edition, Grokking Machine Learning, Grokking Software Architecture, Microservices Patterns, Second Edition and Grokking Machine Learning, Second Edition.
What should I know before learning event?
Manning books that teach event usually introduce JavaScript, Document Object Model, JSON and handler first.
What is the difference between event and command?
A software event is an occurrence, state change, or notification that a system can detect, record, communicate, or handle. A command is an instruction or representation of a requested operation that a system can execute, often with parameters and potentially changing state.
What kinds of event are there?
Kinds of event include exited event.
What is event part of?
Event is part of job. A unit of queued work consisting of event data and a callback that handles the event.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




