Multi-tenancy vs multiple-instances

[matt-beanland]

Given that diffo is about enabling network entities (which may be independent organisations or sub-groups within them) to each operate their own TMF service and/or resource management, we generally would prefer multiple independent instances of diffo (or anything else) to be operated completely independently. The alternative is multi-tenancy, however tenants don't live 'rent free', they are subject to the whims of the landlord who may inflict conditions and requirements on them, particularly with regard to forced upgrades, etc.

That said, for development and demo we may want to operate diffo where we simulate or demonstrate multiple 'entities' using the diffo instance, or using different diffo instances. Currently ash_neo4j only allows a connection to a single neo4j instance, and doesn't make use of any enterprise features so is currently limited by community to a single database. Using cloud, docker etc it is relatively easy to access/standup multiple instances, so it would be possible to at least run multiple diffo applications each with their own database.

Other options to explore may include extending ash_neo4j to use DozerDB which is an extension for neo4j community edition installed as APOC which offers some enterprise features including multiple databases and better indexing (required for vector embeddings?).

Anyway this discussion is to explore what is required/possible.