Event driven didcomm architecture document

[hugoib]

As on the wallet, we produced an architecture document outlining the service layer input/outputs and flows.

https://github.com/adorsys/eudiw-app/tree/main/docs/service-layer

This ticket is about creating an architecture document that will outline the implementation of didcomm with an event service layer.

[hugoib]

Basis for document: Adorsys.pdf

[IngridPuppet]

I quickly went through the current state of the document and agree with the main steps:

• Alice registers with mediator
• Bob adds contact
• Bob sends a message routed via mediator
• Alice checks status requests (messages as per my understanding)

Maybe you are already considering that Bob adds Alice's contact via an OOB invitation that she produces as well. I would just stress that the first step (Alice registers with mediator) is the most important now, and it should be extended to cover the mediator coordination dance, including mediation request and keylist update.

[hugoib]

Status: https://github.com/ADORSYS-GIS/wallet-vc-libs/tree/42-architecture-docs/docs/service-layer

[hugoib]

MR: #49

[nitch2019]

@hugoib is back to you. Please check

[hugoib]

Improved the part of messages sync between FE and BE providing a more robust solution. Back to reviewal.