I would rate this solution as seven out of ten. I have learned a lot from working on BizTalk server. There are new features we can implement in that time. For transactions, they can simplify all of the values for schema-free use. If they want to pick one field from the schema, they can write an excerpt in the expression shape and the orchestration. There's an advantage with using BizTalk. Basically, BizTalk is an XML to XML transaction, so it's better to use BizTalk server. My advice is to understand the client's expectations. Do they want a more secure way of using third party services? Based on their requirements, we can determine whether they should use BizTalk or upgrade to Azure. If someone wants to use BizTalk, they need to buy VMs and install Visual Studio, SQL Servers, and BizTalk Server. They also need to buy all of the licenses. They will need Microsoft support initially for deployment, Azure, and maybe even DevOps tools. If they install BizTalk Server in a different way, they will want to deploy the DLLs and SSLs to PowerShell scripts in DevOps. DevOps lays out the activities they're using. If there are heavy transactions in the SQL Server, they have to upgrade their sequencer hosts and DVs. I would recommend Azure instead of BizTalk. For Azure integrations, there are also API capabilities. Right now, my organization is using Azure, so they're using SFTP folders, but it's intermittent service. All of these activities have moved to the cloud. It's a more secure way of data transactions through the use of tokens. It can be restricted, and you can convert it into API and bond policies. It's more secure.
My advice to anyone considering implementing BizTalk into their organization would be to consider something newer because BizTalk is losing its value. It has been replaced with Azure Functions or Azure Applications. Overall, I would rate BizTalk Server a five out of ten. It is not modern, however, it is alive and kicking.
From a stability standpoint, I would rate the solution 9.5 out of 10. From a manageability standpoint, it's more like a 7 out of 10. Overall, I would rate it at 8.5 out of 10.
You need to consider a modern system instead of BizTalk Server. I rate it a two out of ten.
I would rate this solution as seven out of ten. I have learned a lot from working on BizTalk server. There are new features we can implement in that time. For transactions, they can simplify all of the values for schema-free use. If they want to pick one field from the schema, they can write an excerpt in the expression shape and the orchestration. There's an advantage with using BizTalk. Basically, BizTalk is an XML to XML transaction, so it's better to use BizTalk server. My advice is to understand the client's expectations. Do they want a more secure way of using third party services? Based on their requirements, we can determine whether they should use BizTalk or upgrade to Azure. If someone wants to use BizTalk, they need to buy VMs and install Visual Studio, SQL Servers, and BizTalk Server. They also need to buy all of the licenses. They will need Microsoft support initially for deployment, Azure, and maybe even DevOps tools. If they install BizTalk Server in a different way, they will want to deploy the DLLs and SSLs to PowerShell scripts in DevOps. DevOps lays out the activities they're using. If there are heavy transactions in the SQL Server, they have to upgrade their sequencer hosts and DVs. I would recommend Azure instead of BizTalk. For Azure integrations, there are also API capabilities. Right now, my organization is using Azure, so they're using SFTP folders, but it's intermittent service. All of these activities have moved to the cloud. It's a more secure way of data transactions through the use of tokens. It can be restricted, and you can convert it into API and bond policies. It's more secure.
My advice to anyone considering implementing BizTalk into their organization would be to consider something newer because BizTalk is losing its value. It has been replaced with Azure Functions or Azure Applications. Overall, I would rate BizTalk Server a five out of ten. It is not modern, however, it is alive and kicking.
From a stability standpoint, I would rate the solution 9.5 out of 10. From a manageability standpoint, it's more like a 7 out of 10. Overall, I would rate it at 8.5 out of 10.