Open Closed

Issues with Microservice development #4112


0
nirmaldeol created
  • ABP Framework version: 6.0.0
  • UI type: Angular
  • DB provider: MongoDB
  • Tiered (MVC) or Identity Server Separated (Angular): yes

I have been trying to use your solution to create POC for feasibility POC for microservice solution. I have some issue written ahead. It will be nice if these can be addressed. They are in order of their priority.

  1. Microservices angular code need to developed in separate teams and its possible but you angular solution need to be updated to LaptonX every time we use ABP suite manually.
  2. When we generate ABP suite Microservice or module solution there is no option for mongoDB only solution so I had to convert Entire solution to MongoDB manually for microservice and Modules
  3. Dynamic Permission was another issue which has been presented yesterday in ABp talk If any documentation on that will be welcomed.
  4. All Charts on your theme are static. Evenif I create them will chart.js There is no style guide from ABP how to implement you LeptenX styles .
  5. It will be great if these microservice solution is designed to work with multiple independent teams working on same UI and separate module.
  6. If we are going for enterprise level product we should have some way of custom defining these Abp suite templates or its a pain to keep updating them every time we generate them .

All this feedback should be taken in good faith . I have used your solution (ASPnet boilerplate , ASPNET Zero ) in past and impressed by quality of you product. I hope it to be improved by this feedback.

fyi. My person subscription was until 30th. Will try to update only if org thinks POC is good enough for our microservice architecture with 4+ teams .


1 Answer(s)
  • 0
    gterdem created
    Support Team

    Microservices angular code need to developed in separate teams and its possible but you angular solution need to be updated to LaptonX every time we use ABP suite manually.

    ABP Suite is does not support microservice development completely. If you want to build the UI separately, I recommend building modules (module template) first then convert to microservices.

    When we generate ABP suite Microservice or module solution there is no option for mongoDB only solution so I had to convert Entire solution to MongoDB manually for microservice and Modules

    Yes, we have the issue in our backlog however because of microservice complexity, it will take some time to implement it on our side. Currently, only way to use mongo db is manually configuring it unfortunately

    Dynamic Permission was another issue which has been presented yesterday in ABp talk If any documentation on that will be welcomed..

    Dynamic Permission system is a recent addition with ABP version 7. We are preparing documentation for it, please stay tuned.

    All Charts on your theme are static. Evenif I create them will chart.js There is no style guide from ABP how to implement you LeptenX styles .

    I do not have complete experience on LeptonX styling for charts but if you can create a specific issue based on a specific sample, we'll try to solve the issue.

    It will be great if these microservice solution is designed to work with multiple independent teams working on same UI and separate module.

    There are basically two ways of UI development for microservice development;

    • Modular UI development that the UI is developed inside the module itself.
    • Monolith UI development within the application itself.

    Multiple teams working in different repos of same module UI is not possible. Module can be hosted in a different repository and can be developed individually. That comes to the first question answer; I would recommend building modules first in different repositories then converting into microservices.

    If we are going for enterprise level product we should have some way of custom defining these Abp suite templates or its a pain to keep updating them every time we generate them .

    I am not sure what do you mean by custom defining suite templates but, suite will generate code nicely for modules considering it is has flaws for microservice code generation.