The best architectural solution

I am creating an application that (currently) consists of one web application (ASP.NET MVC) and two console applications.

A web application is just a user interface. The first console application is a service that runs at a certain interval and resets multiple web pages. The second console application is responsible for sending information from my "Downloader" by mail. My console applications run on different computers. The user interface displays the result from the bootloader.

The procedure is as follows:

When a user adds a URI to clean the user interface, the uri is stored in the SQL Server table. My “loader” then selects all the uris and clears them and inserts them into the result table and distribution table. My "Mail Sender" then selects all the rows from the distribution table and sends the information to the user.

Is this an “optimal” solution, or can I optimize it in any way? It’s very difficult for me to support now. Maybe I can use WCF for direct communication between my applications?

The reason console applications run on different computers is because Downloader needs to be connected to a VPN, from which I cannot send mail.

+3
2

NServiceBus -.

+3
0

Source: https://habr.com/ru/post/1730512/


All Articles