Using dapr as abstraction layer between connector and custom infrastructure

[ArzelaAscoIi]

In one of our projects we are using dapr as an abstraction layer between heterogeneous applications, written in various languages and databases.

Dapr is a portable, serverless, event-driven runtime that makes it easy for developers to build resilient, stateless and stateful microservices that run on the cloud and edge and embraces the diversity of languages and developer frameworks

For the idsa-connector, dapr could provide the added value of abstracting arbitrary databases through a rest api. At the same time, dapr could serve as an abstraction between different pub/sub systems in the future.
Since dapr forms a REST API for states (databases, filesystems, s3, azure blob,...) it might be possible to map artifacts to these endpoints. This could allow the idsa-connector to connect to any database in the cloud or on prem.

However, I'm not sure if dapr adds the desired value to the existing infrastructure and I'm not 100% familiar with the architecture and features of the connector, but maybe it helps :)