1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
//! # Evento - Event Sourcing and CQRS Framework
//!
//! Evento is a comprehensive library for building event-sourced applications using Domain-Driven Design (DDD)
//! and Command Query Responsibility Segregation (CQRS) patterns in Rust.
//!
//! ## Overview
//!
//! Event sourcing is a pattern where state changes are stored as a sequence of events. Instead of persisting
//! just the current state, you persist all the events that led to the current state. This provides:
//!
//! - **Complete audit trail**: Every change is recorded as an event
//! - **Time travel**: Replay events to see state at any point in time
//! - **Event-driven architecture**: React to events with handlers
//! - **CQRS support**: Separate read and write models
//!
//! ## Core Concepts
//!
//! - **Events**: Immutable facts representing something that happened
//! - **Aggregates**: Domain objects that process events and maintain state
//! - **Event Handlers**: Functions that react to events and trigger side effects
//! - **Event Store**: Persistent storage for events (SQL databases supported)
//! - **Snapshots**: Periodic state captures to optimize loading
//!
//! ## Quick Start
//!
//! ```no_run
//! use evento::{EventDetails, AggregatorName};
//! use serde::{Deserialize, Serialize};
//! use bincode::{Decode, Encode};
//!
//! // Define events
//! #[derive(AggregatorName, Encode, Decode)]
//! struct UserCreated {
//! name: String,
//! email: String,
//! }
//!
//! // Define aggregate
//! #[derive(Default, Serialize, Deserialize, Encode, Decode, Clone, Debug)]
//! struct User {
//! name: String,
//! email: String,
//! }
//!
//! // Implement event handlers on the aggregate
//! #[evento::aggregator]
//! impl User {
//! async fn user_created(&mut self, event: EventDetails<UserCreated>) -> anyhow::Result<()> {
//! self.name = event.data.name;
//! self.email = event.data.email;
//! Ok(())
//! }
//! }
//!
//! #[tokio::main]
//! async fn main() -> anyhow::Result<()> {
//! // Setup SQLite executor
//! let pool = sqlx::SqlitePool::connect("sqlite:events.db").await?;
//! let executor: evento::Sqlite = pool.into();
//!
//! // Create and save events
//! let user_id = evento::create::<User>()
//! .data(&UserCreated {
//! name: "John Doe".to_string(),
//! email: "john@example.com".to_string(),
//! })?
//! .metadata(&true)?
//! .commit(&executor)
//! .await?;
//!
//! // Load aggregate from events
//! let user = evento::load::<User, _>(&executor, &user_id).await?;
//! println!("User: {:?}", user.item);
//!
//! Ok(())
//! }
//! ```
//!
//! ## Features
//!
//! - **SQL Database Support**: SQLite, PostgreSQL, MySQL
//! - **Event Handlers**: Async event processing with retries
//! - **Event Subscriptions**: Continuous event processing
//! - **Streaming**: Real-time event streams (with `stream` feature)
//! - **Migrations**: Database schema management
//! - **Macros**: Procedural macros for cleaner code
//!
//! ## Feature Flags
//!
//! - `macro` - Enable procedural macros (default)
//! - `handler` - Enable event handlers (default)
//! - `stream` - Enable streaming support
//! - `sql` - Enable all SQL database backends
//! - `sqlite` - SQLite support
//! - `postgres` - PostgreSQL support
//! - `mysql` - MySQL support
pub use *;
pub use *;
pub use *;
pub use *;
pub use *;
use ;
use Ulid;
use crateCursor;
/// Stream utilities for working with event streams
///
/// This module provides stream processing capabilities when the `stream` feature is enabled.
///
/// ```no_run
/// use evento::stream::StreamExt;
/// ```
/// Database migration utilities
///
/// This module provides migration support for SQL databases. Migrations are automatically
/// included when using any SQL database feature (sqlite, postgres, mysql).
///
/// ```no_run
/// use evento::migrator::{Migrate, Plan};
/// ```
/// Event with typed data and metadata
///
/// `EventDetails` wraps a raw [`Event`] with typed data and metadata. This provides
/// type-safe access to event payloads in event handlers and aggregators.
///
/// # Type Parameters
///
/// - `D`: The type of the event data (must implement [`AggregatorName`] and be decodable)
/// - `M`: The type of the metadata (defaults to `bool`, must be decodable)
///
/// # Examples
///
/// ```no_run
/// use evento::{EventDetails, AggregatorName};
/// use bincode::{Encode, Decode};
///
/// #[derive(AggregatorName, Encode, Decode)]
/// struct UserCreated {
/// name: String,
/// email: String,
/// }
///
/// // In an event handler
/// async fn handle_user_created(event: EventDetails<UserCreated>) -> anyhow::Result<()> {
/// println!("User created: {} ({})", event.data.name, event.data.email);
/// println!("Event ID: {}", event.id);
/// Ok(())
/// }
/// ```
pub use MySql;
pub use Postgres;
pub use Sqlite;
/// Cursor for event pagination and positioning
///
/// `EventCursor` represents a position in the event stream. It contains the event ID,
/// version, and timestamp to enable efficient pagination and resuming from specific points.
///
/// This is primarily used internally for event stream pagination and subscription tracking.
/// Raw event stored in the event store
///
/// `Event` represents a single immutable event in the event stream. Events are the
/// fundamental building blocks of event sourcing - they represent facts that have
/// occurred in the domain.
///
/// Events are typically not used directly in application code. Instead, use
/// [`EventDetails`] which provides typed access to the event data.
///
/// # Fields
///
/// - `id`: Unique identifier for the event (ULID)
/// - `aggregator_id`: ID of the aggregate this event belongs to
/// - `aggregator_type`: Type name of the aggregate
/// - `version`: Version number of the aggregate after this event
/// - `name`: Event type name
/// - `routing_key`: Optional routing key for event distribution
/// - `data`: Serialized event data (bincode)
/// - `metadata`: Serialized event metadata (bincode)
/// - `timestamp`: Unix timestamp when the event occurred
///
/// # Examples
///
/// Events are usually created through the [`create`] and [`save`] functions:
///
/// ```no_run
/// use evento::create;
/// # use evento::*;
/// # use bincode::{Encode, Decode};
/// # #[derive(AggregatorName, Encode, Decode)]
/// # struct UserCreated { name: String }
/// # #[derive(Default, Encode, Decode, Clone, Debug)]
/// # struct User;
/// # #[evento::aggregator]
/// # impl User {}
///
/// async fn create_user(executor: &evento::Sqlite) -> anyhow::Result<String> {
/// let user_id = create::<User>()
/// .data(&UserCreated { name: "John".to_string() })?
/// .metadata(&true)?
/// .commit(executor)
/// .await?;
/// Ok(user_id)
/// }
/// ```
/// Trait for domain aggregates that process events
///
/// `Aggregator` defines the contract for objects that maintain state by processing events.
/// Aggregates are the core building blocks in event sourcing - they represent domain entities
/// that rebuild their state by replaying events from the event store.
///
/// # Implementation
///
/// Instead of implementing this trait manually, use the `#[evento::aggregator]` attribute macro
/// which generates the implementation automatically based on your event handler methods.
///
/// # Requirements
///
/// Aggregators must:
/// - Implement `Default` (initial empty state)
/// - Be `Send + Sync` for async processing
/// - Be serializable with `bincode::Encode + bincode::Decode`
/// - Be `Clone`able for snapshots
/// - Implement [`AggregatorName`] for type identification
/// - Be `Debug`gable for diagnostics
///
/// # Examples
///
/// ```no_run
/// use evento::{Aggregator, AggregatorName, EventDetails};
/// use serde::{Deserialize, Serialize};
/// use bincode::{Encode, Decode};
///
/// #[derive(AggregatorName, Encode, Decode)]
/// struct UserCreated {
/// name: String,
/// email: String,
/// }
///
/// #[derive(Default, Serialize, Deserialize, Encode, Decode, Clone, Debug)]
/// struct User {
/// name: String,
/// email: String,
/// is_active: bool,
/// }
///
/// #[evento::aggregator]
/// impl User {
/// async fn user_created(&mut self, event: EventDetails<UserCreated>) -> anyhow::Result<()> {
/// self.name = event.data.name;
/// self.email = event.data.email;
/// self.is_active = true;
/// Ok(())
/// }
/// }
/// ```