Our great sponsors
-
Hangfire
An easy way to perform background job processing in .NET and .NET Core applications. No Windows Service or separate process required
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Build another system to handle calls to quotation engine API , using the request stored in DB & save the response( quotation ) back in DB. Check Background Service documentation. Check Hangfire. Check RabbitMq if you need messaging, queues etc. I am sure more experienced people around here can point you to other solutions.
Build another system to handle calls to quotation engine API , using the request stored in DB & save the response( quotation ) back in DB. Check Background Service documentation. Check Hangfire. Check RabbitMq if you need messaging, queues etc. I am sure more experienced people around here can point you to other solutions.
There's a bunch of ways to do this, the most classical being "service classes". I'm not doing a lot of .NET anymore, but my preferred way of handling these types of things would be MediatR, not because of the actual mediator pattern, but simply because I appreciate how it nicely encapsulates each "feature".
Related posts
- Resources for organizing and maintaining code?
- Exception handling between controller and service
- Is MediatR the only real CQRS solution for .Net?
- I don't get why I should use Redux
- .NET-compatible scripting languages for users to write their own scripts to query/manipulate objects/properties in the app