BizTalk is middleware. It integrates different systems, like ERP and CRM solutions. For some systems, BizTalk has built-in adapters, while for others, we either develop custom adapters or use third-party ones to establish connections.
The easiest route - we'll conduct a 15 minute phone interview and write up the review for you.
Use our online form to submit your review. It's quick and you can post anonymously.
BizTalk is middleware. It integrates different systems, like ERP and CRM solutions. For some systems, BizTalk has built-in adapters, while for others, we either develop custom adapters or use third-party ones to establish connections.
Compared to the current solutions I use, like Azure Logic Apps and other cloud services, BizTalk was far better and more reliable.
Right now, we face data loss due to timeouts and other restrictions when using Azure Logic Apps and similar features. For instance, in Logic Apps, we can't use very large SQL queries. If a query doesn't execute within two minutes, it automatically times out – the default Logic App timeout is five minutes.
However, we didn't have these kinds of limitations with BizTalk Server. Additionally, BizTalk Server offers superior speed and faster processing.
It is easy for a beginner to learn to use BizTalk Server for the first time. It is low-code and relies on configuration instead of extensive coding, so it's considered low-code.
I'm not sure if BizTalk will survive much longer. Microsoft already offers a cloud-based alternative – Azure Logic Apps. With the shift towards cloud computing, most companies will likely choose Logic Apps if they need Microsoft technologies for a BizTalk replacement. There are other competing technologies out there as well.
If Microsoft wants BizTalk to remain competitive, they need to address the cost factor. Other technologies are less expensive compared to BizTalk.
Additionally, 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.
I started using BizTalk in 2010 and worked with it until around 2016 or 2017.
Since then, I've had projects where BizTalk wasn't heavily used – we had an existing application that needed minor changes in XSLT. However, the core functionality of BizTalk hasn't been in use for the last four or five years.
We aren't actively developing in BizTalk, but the migration from BizTalk requires a good understanding of its concepts for a smooth transition.
Initially, there were cloud options, but those weren't widely adopted, so they were removed. Now, we typically install BizTalk Server on a virtual machine within an on-premises setup.
BizTalk was stable. However, it's becoming somewhat obsolete due to the rise of open-source alternatives. As a result, most companies are migrating away from BizTalk due to cost and its limited cloud support.
Nowadays, very few people actively use BizTalk for new development. Most are involved in migration projects, converting BizTalk logic to technologies like MuleSoft, Azure, and other competitors. Now, everything is going to cloud, this is where BizTalk guy with experience to understand the existing logic and convert it to other technologies is required.
Currently, I work with ADA Logix, Function Apps, and BizTalk at another company. We've to migrate from BizTalk, so a basic understanding is necessary to transition the application into ADA or Logic Apps.
When BizTalk Server was new to us, we would copy the MSI and bindings manually from one server to another. But later, when we adopted CI/CD practices, deployment became much easier. With CI/CD, it was a one-click process. Setting up the CI/CD pipeline requires configuring server environment variables. But, after that initial setup, it's easy to use and deploy.
BizTalk Server is not freeware. There's a significant licensing cost involved. Be sure you will actually utilize its features fully. In my previous organization, we weren't taking advantage of BizTalk's capabilities, yet we were paying for it.
If you're not using BizTalk's full feature set, it's a waste of money. We eventually realized this and were able to achieve the same type of manipulations using .NET code without BizTalk. They later removed BizTalk completely. So, my advice is to carefully consider whether you'll truly benefit from BizTalk's features before investing in it.
If I disregard cost and the lack of native cloud support, I'd rate it a seven out of ten. It's reliable when configured properly. However, compared to the technology I'm currently using (Azure Logic Apps), I face issues with timeouts and resource constraints. For that reason, I'd rate my current experience lower.
The primary use case for BizTalk Server is within the shipping industry environment. Our organization relies heavily on electronic data interchange for government invoices and related system data.
The platform's most valuable feature is code integration.
The product could be improved in monitoring, managing, and support functionalities. Specifically, enhancements in monitoring and logging capabilities and better support for administrative tasks would be beneficial.
We have been using BizTalk Server for 3 years.
The product is stable. It has been in operation for more than 24 years.
We have 60 BizTalk Server users in our organization.
We have contacted the technical support services.
Positive
The switch to BizTalk Server was driven by the company's preference for using Microsoft products exclusively.
The initial setup of the BizTalk Server can be described as complex and challenging. It involves tightly coupled configurations, particularly when transitioning to multi-load balancing environments and multiple architectures.
I am not familiar with the platform's pricing details. However, based on the knowledge, it is relatively cheaper than Azure Identity Services and cloud services in general.
It is a legacy system with reliability and extensive features in one package. It is easy to integrate with third-party solutions. We have some 22 built-in adapters with Microsoft, which you can use to connect to older or newer versions.
It takes around six months to understand everything about the BizTalk server. When we restart our integration, we have to understand the core concepts of integration. The concepts are more theoretical than practical.
I rate the product an eight out of ten. It is reliable, especially when load balancing or processing millions of messages daily. We can handle a large number of messages without any issues, ensuring that everything runs smoothly.
