-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BizTalk Server Docker Nano Server image #4
Comments
That would be awesome! |
I asked for that more than a year ago and apparently it's not that easy... But it would definately be great to have that. |
I support this. |
Yes please! |
Totally agree. (Keeping this thread alive) |
Adding @gplarsen |
Yes please |
Need that, too |
With BizTalk Server 2020 in GA, would like to update this feature request to consider adding support for deploying BizTalk container images into Azure AKS, Service Fabric and Azure Arc clusters; both on-prem and in the Cloud. |
This would require an entire redesign of BizTalk :) it would be a new product |
Would love to hear from others and the Azure Integration team but from personal coal face experience, customers expect modern integration solutions to be offered in both managed & self-hosted options. For example compare BizTalk Server 2020 with Mule Anypoint Runtime Fabric. PS. I have full confidence in the the amazingly smart people at MS.. just look at what they are doing in the WSL2 space... above feature is more a question of ROI and customer demand, prioritization etc? |
Not an expert on internals of BizTalk, I think few below steps will be a big leap forward towards modernizing BizTalk without redesigning it:
I am pretty sure there are more things to take care of and please ignore my ignorance, I think though none of this should require a complete redesign of core messaging engine, but a commitment to technology for future. I wouldn’t be surprised if BizTalk is phased out by large enterprises in coming years without this commitment. |
Release BizTalk Server as a Docker Nano Server image
The text was updated successfully, but these errors were encountered: