1

My website currently has multiple windows servers , all of them local in intranet, and each of them have the same source code in the same folder. Currently my workflow is every time I want to Live a new feature, I have to copy and paste to each of those servers. It's getting tedious now since I have around 10 servers, and there have been cases of my colleagues and I missing a server.

We have been looking at separate centralized clustered storage (like Gluster) to store the source code, and we just upload to one point and it will propagate, and we just link it through shared folder in microsoft IIS.

My questions are :

  1. Is there any benefit to doing this? or is it only going to make the website slow?

  2. If it's making the website slower, is there a better way of doing this?

Thanks, I appreciate your time reading or responding to my post.

hafwan
  • 23

1 Answers1

1

Is there any benefit to doing this?

Yes. 1 POF is better than 10

or is it only going to make the website slow?

  • Maybe slower than with local storage
  • I, personally, prefer to avoid Windows-shares in Production

I think, fully automagic CD, which deploy (on conditions met) from single central point to all IIS-hosts may be more bullet-proof solution

NB: I'm far away from real server-management for decades

Lazy Badger
  • 3,157