We're planning to implement Web Farm for our ASPNET Zero application (MVC + jQuery, not Core). We're wondering how things like replication of uploaded files, db record locking, session state, hangfire background jobs will be handled?
AspNet Zero has many features, is there anything major that will be affected if we implement web farm?
Do we need to do any configuration in our project or it is all based on IIS, load balancer etc?
Can someone please explain things that are supported OOTB for web farm and the most infrastructure efficient way to achieve web farming?
3 Answer(s)
-
1
Hi @smartlayer
For the last a few versions, we are storing uploaded files in DB or in a memory cache. If you use something like REDIS instead of memory cache, this will not be a problem for you.
Session management will not be a problem since we use cookie based auth.
You need to work on Background jobs and Notifications (SignalR). You can enable background jobs in one instance for example.
This is not handled by AspNet Zero out of the box.
-
0
Thanks @ismcagdas
We are using custom implementation for file uploads and they are being stored in file system. I guess we'll be better off using a unc path to avoid replication of files. Do you have any other suggestions?
-
0
@smartlayer Nothing that comes to my mind now but if you face any problems, we will be happy to help you.
