Day - 3: Step by Step tutorial for ASP.Net Hosting Environment: IIS, ARR, Web Server Farm, DFS-R

แชร์
ฝัง

ความคิดเห็น • 2

  • @smhaider1333
    @smhaider1333 5 ปีที่แล้ว +1

    Hi @Mahmudur Rahman , Thanks for the video guidance , however I have a scenario : My application receives web hooks from a different source frequently which are relatively fast and events received from those webhooks are transported to clientside using signal R . Now currently we have a single server where this cycle is being executed now we are planning to achieve distributed execution of our current scenario and for that we are bit confused about caching the events as events must be in a particular order.
    My question is : if IIS-A gets an event and stored in cache of webfarm and suddenly goes down after it and load balancing will route the next events to IIS-B , would the IIS-B resume event execution with the already stored events in webfarm cache ?

    • @mroyon
      @mroyon  5 ปีที่แล้ว

      Just few things to ask, is it necessary to use cache of webfarm for your scenario? What kind of data and for how long you want to put it in the cache? Is it just you put the event in the cache and after using that data you remove from the cache. What are you planning to use for cache storage?
      If you have load balancing for IIS-A and IIS-B, and from the question, Im guessing its a fail over scenario. If the webfarm cache is using shared storage and has been configured in such manner to serve independently, mean to say not depending on the IIS, then yes IIS-B will take over from where IIS-A left off. Again it depends on what and how you have configured. My way of thinking would suggest that, make the cache server completely independent from the Web Servers. Weather IIS-A or II-B fails.. it does not affect the cache server. even the scenario would support you to gain high salability. If one cache server is not enough later you can add more node to it.