At a previous employer we primarily used Windows Server 2012 for all systems needs until we decided to build an in-house application and then had to breakdown and buy a server to run Ubuntu Server. Many intranets are comprised completely of Windows devices because of the infrastructure for Active Directory, Remote Storage System, Remote Desktops, and thin clients for users. If I was in this environment again, I would definitely want support for Dgraph with Active Directory ACL. It was a non-profit organization and the company had really discounted licensing and would have no problem deploying more Windows Servers but cringed when we had to deploy a Linux server in an otherwise pure Windows intranet.
So from my POV, Windows support is not really a big factor right now because Dgraph has been for the most part focused on startups which don’t really have a Windows intranet already. But as the enterprise family grows, I definitely see this as being a big issue for organizations who don’t want to use a cloud based service but would rather want an on premise solution in a pure Windows intranet.
Either way, it needs to be clarified on Dgraph’s official Windows support. Either it is only supported for learning and testing and not recommended for production, supported for production, or not supported at all. The downloads page should really make this clear as right now all downloads appear equal across platforms.
There is a quick start guide linked for Docker and Linux, but for Windows it is a download link that just simply downloads the .zip Windows files.
Kubernetes, MacOS, neither have the link to the quick start guide. The Source tab has instructions for compiling from source but make no mention whatsoever about prerequisites of the environment.
I think it is dangerous to make this assumption. IMO. If they are installing Dgraph, most likely they are full system admins and have power to install applications and WSL.
You won’t get more Windows devs coming to Dgraph if they are not supported, simple as that.
The better question to ask is how many Windows devs have came and gone back to Windows SQL Server instead of sticking around and begging for support.
Why be interested in something where you are not welcomed with open arms, but rather told you are not supported.
Hmm… If I was in my previous position and saw a post stating that Windows was not supported for production, why would I bother to share my experience and intentions when it has been clearly stated already that my system is not supported and I need to either use a different database or change my production environment.
Bottom line, I don’t think Windows Devs are gonna stick around to beg for support, they will just go elsewhere or change environments. The later is preferred by Dgraph, but is the former acceptable?