- ABP Framework version: v7.2.1
- UI type: Blazor
- DB provider: EF Core
- Tiered (MVC) or Identity Server Separated (Angular): yes / no
- Exception message and stack trace:
- Steps to reproduce the issue:"
Hi Support Team We are using the ABP commercial infrastructure in our project. ABP Commercial version: v7.1 UI Type: Blazor DB Provider: EF Core Tiered (MVC) or Identity Server Separated (Angular): yes
We are deploying with BlazorServer, Module, Microservice architecture and currently facing several issues.
Issue 1: When we deploy the system with Microservice mode, the main site (MainUI) integrates basic business function modules like Identity UI, Admin UI from ABP commercial microservice. We add our bussiness module like Order UI, EShop UI into one solution, the system can work properly in production environment.
But the customer change their request frequently, mainly in blazor UI part, each release we should restart the host service . it will impact other working service.
Is there a better way to handle that?
1 Answer(s)
-
0
I couldn't understand your scenario clearly.
- You are using microservice template and you are developing modular UI (where you build the UI inside the microservice and the back-office or the public-web application is using project/package reference to it). Is it correct or are you completely using a custom approach?
Issue 1: When we deploy the system with Microservice mode, the main site (MainUI) integrates basic business function modules like Identity UI, Admin UI from ABP commercial microservice. We add our bussiness module like Order UI, EShop UI into one solution, the system can work properly in production environment. But the customer change their request frequently, mainly in blazor UI part, each release we should restart the host service . it will impact other working service.
As far as I understand, you are hosting multiple UIs in a single BlazorServer Host (called MainUI). But whenever a dependend module is changed, you need to reboot the main UI to reflect the changes.
There is not much thing to do in here. That is an effect of running combined UIs in a single host. You need to go for micro-frontend approach that hosts the UIs individually so they can be hosted separately and independently. Unfortunatelly ABP doesn't have an infrastructure for micro-frontends.
