Evento Framework
  • Introduction
  • Architecture Overview
    • Distributed Systems & Microservices
    • Recative Manifesto & Reactive Principles
    • State-of-the-art Patterns
      • DDD (Domain Driven Design)
      • CQRS (Command Query Responsability Separation)
      • Event Sourcing
      • Messaging
      • Saga
  • GETTING STARTED
    • Quick Start
    • TodoList - RECQ Tutorial
      • Problem Description and Requirement Gathering
      • RECQ Payload Design
      • RECQ Components Design
      • Set up your Development Environment
      • RECQ Payload Evento Implementation
        • Domain Commands
        • Domain Events
        • Views
        • Queries
      • RECQ Components Evento Implementation with Spring Data
        • TodoListAggregate
        • TodoList Model with Spring Data
        • TodoListProjector
        • TodoListProjection
        • TodoList Invoker
      • Expose the RECQ architecture with Spring Web
      • Test Your App
    • Extend TodoList - Handle Complexity Tutorial
      • Unique identifier generation
      • Extends behaviors with Observer and Services
      • Cross Domain Consistency with Sagas
      • Handle Real time data updates with MQTT and Save-Notify Pattern
  • RECQ Patterns
    • RECQ Patterns
    • RECQ System Pattern
      • Component
      • Message Gateway
      • System State Store
    • RECQ Communication Pattern
      • Component to Component
      • Component to System State Store
      • System State Store to Component
    • RECQ Component Pattern
      • Aggregate
      • Projector
      • Projection
      • Service
      • Invoker
      • Saga
      • Observer
  • Evento Framework
    • Evento Framework Introcution
    • Payload and Messages
      • Command
        • Domain Command
        • Service Command
      • Event
        • Domain and Service Event
      • Query and View
    • @Component
      • @Aggregate
        • Aggregate State
        • @AggregateCommandHandler
        • @EventSourcingHandler
      • @Projector
        • Projector @EventHandler
      • @Projection
        • @QueryHandler
      • @Service
        • @CommandHandler
      • @Invoker
      • @Saga
        • SagaState
        • @SagaEventHandler
      • @Observer
    • Dead Event Queues
    • EventoBundle
      • EventoServerMessageBusConfiguration
      • ConsumerStateStore
        • InMemoryConsumerStateStore
        • PostgresConsumerStateStore
        • MysqlConsumerStateStore
      • Context
      • TracingAgend and @Track
        • SentryTracingAgent
      • Autoscaling Protocol
        • ThreadCountAutoscalingProtocol
      • Injector and @Component
  • Evento Server
    • Evento Server Introduction
    • SetUp Evento Server
      • Advanced Options
      • Evento Event Store Modes: APES and CPES
    • Evento Server Cluster
    • Bundle Deploy Script
  • EVENTO GUI
    • Explore RECQ Systems Visually
    • GUI Auth
    • Payload Catalog
    • Component Catalog
    • Bundle Catalog
    • Cluster Status (Experimental)
    • Flows
      • Performance Evaluation
    • Application Graph
    • System State Store
  • Evento CLI
    • Evento CLI Introduction
    • Update Version
    • Publish
Powered by GitBook
On this page
  1. EVENTO GUI

System State Store

The System State Store page provides a comprehensive view of your system's event history and current state. It comprises two primary components: the Event Store and the Snapshot Store.

PreviousApplication GraphNextEvento CLI Introduction

Last updated 8 months ago

Event Store

The Event Store is an append-only log that records every change made to the system state. Each entry in the Event Store represents an event, capturing the details of the change that occurred.

Event Details:

  • Event Id: A unique identifier for the event.

  • Name: The type of event that occurred.

  • Aggregate Id: The identifier of the aggregate associated with the event.

  • Context: Additional context information related to the event.

  • Timestamp: The time when the event occurred.

By examining the Event Store, you can:

  • Trace System Evolution: Follow the sequence of events to understand how the system has changed over time.

  • Debug Issues: Analyze event history to pinpoint the root cause of problems.

  • Audit System Activity: Review past events for compliance or regulatory purposes.

Snapshot Store

The Snapshot Store contains periodic snapshots of the system's state. Snapshots are created to optimize performance by reducing the number of events that need to be processed to rebuild the current state.

While the Event Store provides a complete and immutable record of system changes, the Snapshot Store offers a more efficient way to access the current state of specific aggregates.

Note: The Snapshot Store is typically used internally by the system and may not be directly accessible to users.

By understanding the relationship between the Event Store and the Snapshot Store, you can effectively navigate and analyze your system's state. The System State Store is a valuable tool for developers, system administrators, and auditors to gain insights into system behavior and performance.

Event Store Section in System State Store
Event Detail