Hi all, Thanks for the responses! Im subscribed to the thread but did not receive update over email so I missed your responses until now. I will clarify some parts here i noticed were not clear.
Hi!
I have some general architecture questions. I'm starting a new project on 4.4.3. The idea is that this will be a multitenant sas app. I will create several modules under the main application, each module will be for a specific webcart software, for example magento, shopify, etc. The implementation of the endpoints that remote carts will call and domain data for each of these is contained inside the module. When new data comes in ( new orders for example ) the module will kick off a distributed event (these will be local initially but the code should work for when we move to microservice, per the docs). The main application then subscribes to these events and should record the transaction locally on abp database, and then schedule and process a background job (using the hangfire implementation) that posts the transactions into the appropriate remote backend.
Does this make sense to do? Also since the background jobs seems to be picked up from the queue sequentially and there could be many jobs and tenants, would we run into a problem where there could be a ton of transactions queued and they'd only be processed sequentially so a particular tenant could see huge delays getting their transactions in?
A bigger concern is the fact that creating a bunch of httpclients to make the outgoing requests to the remote backends could cause resource exhaustion. In the past I've used an httpclient in DI to make the requests, however there's a problem here, and that is that each tenant will configure via settings management their remote backend url, these are different servers (but all the same software so contracts are the same). When the transaction is processed and send to the remote backend, the url will be different because they are different servers. To complicate matters most, the remote backend requires Login -> Receive SesssionID -> Then send this in the header of every subsequent request. In non multi-tenant implementations where its only one backend the application is sending these requests to, i simply use an interceptor to modify the header on the outgoing request.In multi-tenant I assume the best thing to do would be to login -> send to redis cache for the tenant, and check this each time in the future when a request needs to go out and its for a particular tenant ID.
I'm looking for any suggestion on how to accomplish this reliably without collapsing the application, keeping in mind that thousands of transactions can be posted in to the abp app, from different web carts, from different tenants.
I know this is a loaded question. Just looking for direction to make the most of this framework using best practices.
gterdem is the guide out?
Hi There! Can you share the error you're getting? As far as I know any service you create in your application project that ends in AppService is automatically exposed so you can consume it from your web project.
Hello David. I will send you a sample project that DevExpress has been fully implemented.
I'd love this project too :)
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
The documentation at https://docs.abp.io/en/abp/latest/PlugIn-Modules does a decent job of explaining how to work with modules to separate new features on your main application, however all of the examples are for MVC. Is this possible for the angular UI as well? In mvc it seems you just add a new module and add your views, compile and include that somewhere so its loaded up by the main app, would there be a similar process supported for Angular? If not, does that mean that all of the features would have to be implemented for every deployment then since we cant split out module UIs?
Hi,
Thanks for the feedback I'll take a look into it. I see the example is to user razor pages even though my project is implementing apis on the net core and the frontend on angular. Does that mean that the real base of abpio is to use the mvc deployment since some modules seem to rely on it? for example docs module doesnt seem to be available for angular
Should I just switch my entire project over to netcore with mvc to have the largest coverage?
Check the docs before asking a question: https://docs.abp.io/en/commercial/latest/ Check the samples, to see the basic tasks: https://docs.abp.io/en/commercial/latest/samples/index The exact solution to your question may have been answered before, please use the search on the homepage.
The documentation for the commercial payment module says the below. does this mean we can implement other payment systems, if so, wheres the documentation for what we need to do? I dont have the higher level license to download existing pro module code, so documentation on these things is crucial..
Configure<PaymentOptions>(options => { options.Gateways.Add( new PaymentGatewayConfiguration( "MyPaymentGatewayName", new FixedLocalizableString("MyPaymentGatewayName"), typeof(MyPaymentGateway) ) ); });
Same problem if you upgrade existing solution to 4.0.1, angular client stays at gray screen and this can be seen in console.
Cli 4.0 and suite 4.0 Generate a brand new project, build project, add an entity in suite. services are correctly generated on the backend, however UI is not generated on the frontend. reviweing suite log I can see the path to the schemas has .suite\schematics.suite\schematics in it (its duplicated!!) if you generate the path structure inside it as its looking for, it runs and generates the UI. surely this is just a bug with the duplicate path?
example
2020-12-03 10:42:03.931 -05:00 [INF] Running the Angular Schematics command: npx "projectpathhere/angular/.suite/schematics/node_modules/.bin/ng" g ".suite/schematics/collection.json:entity" app-pro CustomerPortal "projectpathhere/aspnet-core/.suite/entities/Customer.json" 2020-12-03 10:42:07.601 -05:00 [INF] Angular Schematics command failed. Collection "projectpathhere\angular**\.suite\schematics\.suite\schematics**\node_modules\@abp\ng.schematics\collection.json" cannot be resolved.