richard-churchman
5f6bbe45f7
Major bug fixes relating to the Redis implementation in Reprocessing and Search Key Cache were identified and fixed as part of the rekeying development. Included functionality to stop the Exhaustive training. Fixed the Unsupervised learning functionality in Exhaustive Training. Embedded the Mock Data CSV data into a class to make it compatible with Docker without needing to modify the Dockerfile (i.e, build). Included a new table that stores training data to enhance support capabilities for Exhaustive. Reintroduced and validated the Multitenancy functionality. Postgres is now fully deprecated in place of Redis for cache, and all implementations of the Interfaces for Postgres have been removed. No migrations exist to support this deprecation, and Postgres as a cache is now wholly unsupported. Removed the Indexing background thread, as Redis does not require it, given that it is a key-value pair database. Created a RedisCommandFlag Environment Variable to support Fire and Forget write to Redis in Invocation. Implemented functionality to Export, Peek and Download configuration environments using a secure, encrypted scheme. Created a permission to access the functionality via the user interface. Extensive database-based logging is included to provide for a comprehensive audit. Created functionality to Import the encrypted Export file inside a database transaction to ensure consistency. As Docker is now the primary deployment model, log4net instantiation has been moved to an approach that primarily uses programmatic instantiation of the ConsoleLogger and RollingFileAppender given Environment Variables. Implemented functionality to support remote \ mounted Log4Net XML Serialisation files for more advanced log4net configurations. Reintroduced access to counters via the user interface and created a permission. Took the opportunity to implement ReSharper linter suggestions. Disabled the Lock button across the whole application, with that functionality being reserved for future use. It is intended that locking happens programmatically on the basis of dependencies in future commits. Fixed several significant end-use bugs which became apparent during testing of the refactored code relating to case management and visualisations. Fixed certain other minor bugs that came up during testing. Brought documentation up to date for this commit. Brought the Docker Compose file up to date for this commit. Removed Redundant Environment Variables for this commit. Made the README file less verbose and unnecessary.
2.1 KiB
layout, title, nav_order, parent, grand_parent
| layout | title | nav_order | parent | grand_parent |
|---|---|---|---|---|
| default | Multi Tenancy Concepts | 1 | Multi Tenancy | Concepts |
🚀Speed up implementation with hands-on, face-to-face training from the developer.
Multi Tenancy Concepts
Jube supports multi-tenancy which allows single infrastructure to be shared among many logically isolated clients (i.e. customers rather than end users rolling up to those customers), maintaining total isolation between tenants data, with no loss of function in the user interface. Given the use of Environment Variables, optionally, Jube threads and cache offloading can be quite selective also, which serves to separate compute where required, why obtaining cost efficiency of centralised configuration.
In Jube, isolation between tenants is rooted at a TenantRegistryId field at the top of various data hierarchies which are joined and predicated for in every query made against the database.
Behind the scenes, for each request made via the API, the tenant registry identifier for the authenticated user is looked up, with that value being used as predication in any database query. For example, suppose the table:
select * from "EntityAnalysisModel"
Returning the follow data:
Note the field TenantRegistryId:
The tenant registry identifier implies that all of the data in this table is owned by TenantRegistryId 1. The EntityAnalysisModel has many child tables which have relationships, henceforth it is not necessary to have the TenantRegistryId on each table, as it can be joined to. For example:
select * from "EntityAnalysisModel" m
inner join "EntityAnalysisModelRequestXpath" x on x."EntityAnalysisModelId" = m."Id"
where m."TenantRegistryId" = 1
The above pattern is applied to every query made available to the API, this for the user interface, having the effect of total isolation between tenants, not withstanding the same physical database instance (unless Cache and Threads are arranged otherwise with Environment Variable configurations).