Skip to content

Commit

Permalink
v0.195.0 - Implemented outbox pattern (#741)
Browse files Browse the repository at this point in the history
Reliable transaction-based internal cross-domain message passing component (`MessageOutbox`), replacing `EventBus`:
 - Metadata-driven producer/consumer annotations
 - Immediate and transaction-backed message delivery
 - Background transactional message processor, respecting client idempotence

Persistent storage for flow configuration events.

Supplementary refactoring:
- Introduced use case layer, encapsulating authorization checks and action validations, for first 6 basic dataset scenarios
   (creating, creating from snapshot, deleting, renaming, committing an event, syncing a batch of events),
- Separated `DatasetRepository` on read-only and read-write parts
- Isolated `time-source` library
- Decoupled repositories from dependency graph.
- Clarified dataset find/get interfaces in dataset repository
- Unified naming of repository structs, files, harnesses
  • Loading branch information
zaychenko-sergei authored Aug 16, 2024
1 parent db57cf1 commit da0db9b
Show file tree
Hide file tree
Showing 436 changed files with 11,051 additions and 3,332 deletions.
12 changes: 11 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,19 @@ All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## Unreleased
## [0.195.0] - 2024-08-16
### Added
- Reliable transaction-based internal cross-domain message passing component (`MessageOutbox`), replacing `EventBus`
- Metadata-driven producer/consumer annotations
- Immediate and transaction-backed message delivery
- Background transactional message processor, respecting client idempotence
- Persistent storage for flow configuration events
### Changed
- Upgraded to `datafusion v41` (#713)
- Introduced use case layer, encapsulating authorization checks and action validations, for first 6 basic dataset scenarios
(creating, creating from snapshot, deleting, renaming, committing an event, syncing a batch of events),
- Separated `DatasetRepository` on read-only and read-write parts
- Isolated `time-source` library
### Fixed
- E2E: added additional force off colors to exclude sometimes occurring ANSI color sequences
- E2E: modify a workaround for MySQL tests
Expand Down
Loading

0 comments on commit da0db9b

Please sign in to comment.