...
- Borrows concepts from Distirbuted Data Servcies, Blockchain, STS
- Not limited to a blockchain implementation in anyway
- Can use STS for trust verification optionally
- Operates as a service via API or agent
- Provides interfaces for extension services
- Configuration by file or variables
- Segregates roles for transaction sources and consumers
- Supports listeners for consumer services optionally
- Defines control blocks for faster processing on transaction apply or undo
- Provides search filters by time, by block, by transaction ID, by attributes or combinations of criteria
- Provides accurate time series transaction state change tracking for any transaction services ( SQL, NOSQL, API, RPC etc )
- Optionally tracks post transaction state, pre and post transaction state or state changes only
- Platform independent service
- Can run asynchronously minimizing performance impacts of transactions
- Provides listeners for reactive event management
- Can be used to recover transactions
- Idempotent transactions repeated create the same state footprint except for timestamps, status and origin
- SCM life cycle for transactions - transaction request > route > notifications ( synch and asynch ) > execution > commit > notifications ( synch and asynch ) > finalization > notifications ( synch and asynch )
- asynch processing can be done as parallel thread, callback, state db change updates, SSE ( server sent events )
VSC >> Virtual Smart Contact - a smarter smart contract
...