The most valuable feature is its reliability and stability. The first version of BizTalk was released in 2000, and many companies still use it. It was stable until 2013 when we had support.
Essentially, you can do whatever you like with these systems, and you do not have to take care about the scaling because if one server is overloaded, it just forwards the message to the next server, even if it were designated to a specific server. It weeds out the messages according to the load. If you want to scale it, you just add new servers.
It's an on-premises system, requiring physical servers for deployment. This is different from Azure; you don't need any servers with Azure. If you have a subscription, you can do whatever you want. There are unit restrictions based on the environment (like non-production vs. production) in BizTalk. You need physical servers and databases. In Azure, those are not required – it's all in the cloud.
Development Team Lead at a media company with 51-200 employees
Apr 18, 2024
BizTalk lacks native cloud support. BizTalk doesn't offer in-built support for cloud. We need to use third-party adapters to connect it to cloud services.
It's a complex product because you have many degrees of freedom to connect different parts together. Whether it's sensible or not, is up to you, but the machine does allow it. But because of the vast degrees of freedom, it's complex.
