the answer is https://commercial.abp.io/faq#what-happens-when-license-ends tldr; you can use it forever (perpetual license) you will still login in development mode but you'll not be able to get the latest major updates.
I agree that 4sec is too much for that appservice method. then there's a problem with the database server. can you add Dapper to your project and write a raw sql without using ABP repositories. If the duration is still long it means there's a slowness at the database server.
@rafal, 4.4.2 will be released this weekend but I'm sorry that this feature will not be included in 4.4.2. because the PR is still under revision. we don't want to have an issue on this important feature. probably next release you can get it.
_identityUserAppService.GetListAsync makes 2 DB request. one for count one for the list. and I think this duration is OK. 1.44second is acceptable with a fully featured request.
Do you say it adds 300ms when you derive from AbpController?
See the AbpController base class which uses Lazy properties.
hi piseth,
we got your project. we'll inspect and get back to you soon.
@rafal this feature will be in 4.4.2. 4.4.1 will be released this week.
Product service is not identical to a standard ABP microservice module. Try to add a new service and use Suite on the new standard service.
this is fixed in 4.4.1 wait next week
the next version comes with a feature that fits houtt requirement. ABP Suite will be able to connect a database and create full stack CRUD page. awai.
GetPositionLookupAsync() takes 100ms . i think it is OK. your service provider has a 100ms lag with the empty action.
1- add auditing and authorization attributes and report duration. 2- make a db transaction and report duration.
we will see which step adds the overhead
