Thank you for your interest.
Right now it seems every user needs to make the choice between Docker for Azure and Azure Container Service, yet the offerings seem overly similar. We’d love a clear answer as to what the respective vision of each offering is, or even better a proper and current comparison (both technical and non-technical).
We’re in that position of having to choose right now; we tested ACS more than a year ago and were a bit dissatisfied with how bare bones it was at the time. We’ve been playing with D4A for a few months now and are quite pleased with the level of integration (e.g. with the LB). Since, it looks like ACS has evolved a lot, with Microsoft even spawning interesting complements like ACI. So now we feel like we should test it again just to make sure we understand the difference as things stand today, if there are any (we aim to deploy our application on a Swarm this month or the next).
This kind of back-and-forth during evaluation phases feels a bit unnecessary when there is no clear documented product differentiation between the two (that we can see, anyway). We’ll probably do our job and commit to one and hopefully never look back, but I imagine all other new users will have the same (currently unanswered) questions after us. If there is truly no reason (other than historical reasons or purely as an effect of Conway’s law) for the existence of two independent offerings, then it would make sense to me that both companies collaborate on all the integration work between Docker Swarm and Azure. AFAICS this could take the form of a shared ARM template.