IIS is easier to configure and manage. Doesn't require deep knowledge of the product to manage it. Doesn't require for IT team to learn Linux/Unix OS for basic web hosting. However, for advanced IT specialists, all three solutions could be useful and can work together.
I use FileZilla to securely upload files that are not permitted to be sent via insecure methods like email or web forms. FileZilla is great to test the ability to "reach" the remote SFTP server and to verify my files arrived. Once I have tested that, then our internal IT group automates the uploads to these third parties, however I can always manually log into FIleZilla to verify the uploads.
Publishing applications or websites is easy with Microsoft IIS. You don't need external software or complicated tutorials involving command lines and editing configuration files. On other hand, sometimes the troubleshooter needs a high knowledge of Windows Server, Registry, and tools to debug the application. If you need to host non-Microsoft technology as PHP pages or have a low budget, I recommend IIS equivalent software as Apache.
Strips away unwanted underlying code from products that produce documents using any Microsoft product that is not needed in our products.
The nice part is that it strips away hidden code such as ctrl and another digit that is not necessary or can be replaced with the correct coding to produce standard processes such as graphics using ANSI or another protocol as well as line feeds and header masks.
We are in the process of determining if their pro product will function in the way we want it to across networks rather than going to each workstation to make changes decreasing our productivity.
We are also evaluating whether their technical support is responsive.
A big advantage that we use all the time is reviewing the logs that automatically get generated in IIS. It has helped us troubleshoot various problems in our applications over the years.
IIS integrates really well with Visual Studio and TFS. We are able to quickly deploy new applications and changes to applications when requested by the business.
IIS has proven that it is easy to configure and maintain with minimal effort.
Website slow to download from - This is a minor gripe, and only a one time thing, but in writing this review I decided to install the latest version of FileZilla just to make sure I was running the latest and greatest. Turns out that it takes 10 minutes to download from their website, on a 50 Mbit dedicated business line.
Some features locked behind Pro - The free version of FileZilla lacks some features that would be nice to have without requiring the upgrade to Pro. However, FileZilla Pro is quite affordable and so if you need integration with Google Drive, OneDrive, DropBox, Box, or many others, then it's definitely worth it.
Auto-update could be improved - I had a version of FileZilla installed and it would not auto update. In fact, Mac OS X required me to remove it, saying that it was malware. I re-downloaded FileZilla again after this, but it was odd. At other times, it seems that FileZilla auto-updates just fine.
We have no intention to replace all applications running on top of the IIS platform. Not all applications support other platforms and not all support staff are skilled in Linux/Apache platform support. Whereas IIS may not be the best performing or most secure web platform available, for the aforementioned reasons, it is impossible not to continue use of this product.
FileZilla is really easy to understand and makes it easy to log into servers to upload files. Moving files around is a breeze (even if it's a little tedious to wait for large quantities to move one by one) and editing html and css files directly is a feature it would be difficult for us to live without
As I've mentioned earlier, Microsoft IIS is very simple and easy to use. The user interface is a little bit overloaded with a huge number of different options, but once you have a little clue of what you are doing and what you need - no issues at all.
ARR (application request routing) in Microsoft IIS Server enables the web-admins to increase the web app reliability and availability through the rule based routing and load balancing of HTTP requests which in turn provides highly available server. IIS 7.0 Manager also provides kernel as well as user mode caching for faster performance and in case if the server fails, the IIS server has good amount of details logged in its log files which help understand and debug the cause quickly. Load balancing facilitates IIS server to fight against availability issues.
In my experience, I have never had significant issues with IIS performance. Sometimes I've experienced issues with loading time, but it is mostly related to the web site code. However Amazon, Microsoft and Google providing free cloud services with very limited resources, and in that scenario, "heavy" websites on IIS could be the issue. In other situations - performance is good.
I've always found the setup of FileZilla to be easy to use and setting up new sites has been quick. In working with FileZilla, I haven't had any issues. I rate it high because it's easy, quick, and free. I think anyone that is familiar with File Explorer can use FileZilla.
As mentioned earlier there is so much documentation or guides or stack overflow questions out there that someone will have faced the same or very similar scenario to what you are going through that you will almost certainly find a solution to what you are after.
Both perform the job they are expected to do, and they are easy to use. The FileZilla software is a desktop-based app, so I can only access it on the device on which it was installed. Cisco Secure Email allows you to send emails as you would normally, but the email and attachments are secure.
Apache is java. Java is unnecessary complex. No developer wants to invest in learning all the hundreds of text based configuration files to get something done. Also, apache gives you the most evil and un-usable user interface possible. [Microsoft] IIS makes [life] after development easy, which is already complex enough to be bothered by something as mundane as exposing your work over the internet.
Microsoft IIS Server is scalable if the underlying server configuration is done correctly. Use x64 edition v/s 32bit and using 32bit mode application pools are some of the tweaks to be done to make the IIS server scalable. There are too many small configurations need to be carried out in order to make a highly scalable IIS server hence not giving full score in this area.
