interfaces and types for Optic SaaS surface area
published 10.3.0 3 years ago- published 0.1.1 3 years ago
Data in Optic goes through many layers of transformation. For examples: - Commands yield Events - Projections consume Events - Aggregates consume Events - Diffs consume Aggregates and Interactions - Reports consume Aggregates and Interactions - DiffDescri
published 10.3.0 3 years ago- published 10.3.0 3 years ago
This workspaces should be called something more general than "diff-engine" because it encompasses most of the Optic domain.
published 10.0.4 3 years ago- published 10.0.4 3 years ago
- published 10.3.0 3 years ago
- published 10.3.0 3 years ago
- published 10.3.0 3 years ago
- published 10.3.0 3 years ago
- published 10.3.0 3 years ago
This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
published 10.3.0 3 years agoThe highest performance way to call the Optic engine by providing native ways to call the Optic engine, enabling concurrency through threads:
published 10.3.0 3 years agoThe (probably) most portable way to call the Optic Engine is by using it's WASM interface. If high performance / concurrency is required, consider using `optic-engine-native`.
published 10.3.0 3 years agoNodeJS middleware for using Optic within ExpressJS
published 0.0.5 3 years agoNodeJS middleware for using Optic within Hapi
published 0.0.6 3 years ago- published 0.25.10 2 years ago
- published 0.25.7 2 years ago
- published 0.54.13 2 months ago
- published 0.54.13 2 months ago
- published 0.54.13 2 months ago
- published 0.22.4 2 years ago