Sons of PHP
Source Code
  • 🏠Home
  • Contributor Covenant Code of Conduct
  • Getting Help
  • Reporting Issues
  • Security Policy
  • 🪈Bard
    • Overview
    • Commands
  • Symfony Bundles
    • Feature Toggle
  • Contracts
    • Contracts Overview
    • Common
    • Cookie
    • CQRS
    • Filesystem
    • Mailer
    • Pager
    • Registry
    • State Machine
  • 📦Components
    • Assert
    • Cache
      • Adapters
      • Marshallers
    • Clock
    • Container
    • Cookie
    • CQRS
    • Event Dispatcher
    • Event Sourcing
      • Aggregates
        • Aggregate Repository
      • Event Messages
        • Using the Serializable Event Message
        • Message Enrichers
        • Message Serializers
        • Message Repository
        • Message Upcasters
    • Feature Toggle
    • Filesystem
      • Adapters
    • Http Factory
    • Http Handler
    • Http Message
    • JSON
    • Link
    • Logger
      • Handlers
      • Enrichers
      • Filters
      • Formatters
    • Mailer
      • Transports
    • Money
      • Currency Providers
      • Operators
      • Queries
    • Pager
      • Adapters
    • Registry
    • State Machine
    • Version
  • 💁Contributing
    • Contributing Overview
    • Contributing Code
    • Discussions
    • Documentation
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. Components
  2. Event Sourcing

Event Messages

Event Messages are what Aggregates will raise and what the Event Message Handlers will handle. Event Messages will also be stored in whatever storage backend you decide to use. They are used to rebuild the Aggregates as well. So as you can see, Event Messages are a big part of Event Sourcing!

Event Messages consist of 1) Metadata and 2) Payload. The Metadata contains information about the event and the aggregate. The payload is the data that is passed in and used to rebuild the aggregates.

PreviousAggregate RepositoryNextUsing the Serializable Event Message

Last updated 8 months ago

Was this helpful?

📦