Event Driven Architecture
The SSI Abstraction and the underlyning framework is Rest API Based, which is for the most use case a little blocking. The entire architecture should be event driven. For instance:
- when a proof event is occuring, it should be published on NATS to react on it
- received or expired credentials should be published on NATS
- incoming connection recevings, as well invitation usages etc. should be published on nats
Other events like status changes are already on nats, but not very well integrated.
I would assume the aries framework extension for REST must be removed/replaced/modified by a event driven extension.