My team and I have been struggling to automate our mostly-Windows infrastructure around us. We’re dealing with old .NET web applications and Windows Services, for the most part. While some are moving on to .NET Core, we’re still having a hard time convincing development teams to consider moving to Linux. Despite this, we’ve gotten better at automating our infrastructure (Terraform & Chef), but we’re having a harder time with application orchestration as a result.
I’m considering a way forward with Nomad since it would not require us to containerize our applications (until teams were ready to) and since we’re already utilizing the other typical components of a Nomad cluster in varying degrees (Consul & Vault). I’ve read about the Nomad IIS driver, so no concern there. But I have had some express concerns about trying to migrate .NET applications that are currently running as Windows Services into Nomad.
These Windows Services usually consume queues on various RabbitMQ clusters we have. There are a few edge-cases that interact with old MSMQ queues or perform some operation that may take authentication for granted (meaning, the Windows Service is running under a domain service account, so things often “just work”). Has anyone had any experience with this? Or does anyone have somewhere I might do some reading? My research hasn’t turned up much, so far.
I’m at the early stages, still. So I’m very open to any suggestions, advice or reading material you may have.