Hi,
We will fix the problem, and your ticket refunded.
You can use the event bus (domain event or your custom event) to save data to DB or Elastic search.
If you already have some data, then you may need to do a data migration.
We have some usage of elasticsearch: https://github.com/abpframework/abp/blob/dev/modules/docs/src/Volo.Docs.Domain/Volo/Docs/Documents/FullSearch/Elastic/DocumentChangedEventHandler.cs https://github.com/abpframework/abp/blob/dev/modules/docs/src/Volo.Docs.Domain/Volo/Docs/Documents/FullSearch/Elastic/ElasticDocumentFullSearch.cs
Hi,
With independent services, the reporting module is more like an infrastructure, you can use it anywhere.
When you have hundreds of tenant independent databases, it's not good to query this data from the tenant's database context. It is better to use a separate database table for reporting.
Do you have any useful links/references that may help us clarify this approach
Sorry, I don't have such links. it's more like our audit logging module, you can check it.
I will make an example for you.
Thanks, we will check it.
Hi,
JWT token is designed to be immutable, but you can create a middleware to change the ICurrentPrincipalAccessor to add the claims.
It should work on the current HTTP request.
But for Blazor server UI. It uses SignalR to synchronize operations, you can create a hub filter.
Hi,
I will check it
Hi,
Why not create a reporting service(module), it has a separate database or NoSQL database, like Elasticsearch? in this way you don't have to query hundreds of tenant databases to get reports.
About performance,
You can create a background worker to generate reports periodically, when you query, it's ready immediately. (not used for real-time reporting)
Hi,
Sorry, we don't have this plan, you can implement it yourself if you need it.
Hi,
sorry I don't quite understand what you mean, as my understanding you can use the suite to load an entity and continue to add property.
