Likelihood to Recommend Experienced a lack of available programming languages while working on a minor project. I had to halt the project and wait for it to be added later. It took ages and had a hit on our productivity. It has a centralized management system which helps and an easy interface which helps to manage multiple tasks in case of large-scale operations and projects.
Read full review BizTalk is well suited as middleware. Where you wish to translate an input file into an output file and send it to some endpoint. In our case, we used it to convert and send files to SAP. In many ways, it very flexible, and you can do almost anything you want with it. In many ways, it's a better solution than your SAP XI or PI as middleware, since it's much less expensive, and allows you do interface with non-SAP systems.
Read full review Pros API Gateway integrates well with AWS Lambda. This allows us to build a web server in the language and framework of our choice, deploy it as a Lambda function, and expose it through API Gateway. API Gateway manages API keys. Building rate limiting and request quota features are not trivial (or interesting). API Gateway's pricing can be very attractive for services that are accessed infrequently. Read full review It is very user friendly. Users can change rules during run time and change workflow. Huge capacity for queueing messages. It supports all types of adapters like Oracle, Salesforce, SMTP, FTP, etc. Also users can built custom adaptors. If users want to dynamically deploy their solution without any downtime, this is a perfect solution. BizTalk will be a good fit, especially for public-facing websites. Well-proven in the market. I used it when developing a website for Virgin Trains, catering more than 800K user requests per day. Helps in load balancing. Read full review Cons Client certificates are troublesome when trying to attach them to API GW stages. Debugging across several services can be difficult when API GW is integrated with Route 53 and another service like Lambda or EC2/ELB. Creating internal/private APIs, particularly with custom domains, can be unintuitive. Read full review Microsoft BizTalk is over engineered for some situtations Microsoft BizTalk can be frustrating to use as it forces you to use the GUI as opposed to code Microsoft BizTalk is very resource intensive to create integrations Read full review Likelihood to Renew BizTalk will always be required at this hospital.
Greg Walia Technical and Application Support Specialist
Read full review Usability I gave a 7 because this product BizTalk does need time and training to get familiar with the usability and features, it is not that easy to use.
Greg Walia Technical and Application Support Specialist
Read full review Support Rating We always had a great experience with the AWS support team. They were always on time and very dependable. It was a good partnership while we worked to resolve our issues.
Read full review BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
Read full review Implementation Rating Make sure you have everybody and all depts. On board during testing on test server.
Greg Walia Technical and Application Support Specialist
Read full review Alternatives Considered When we tested
Azure API Management at the time, it had serious connectivity issues, it was very unstable, and it needed to do a lot using the command line. Comparing with the AWS solution, which was more mature, and the fact that we have services in use on AWS, we ended up choosing to continue using AWS products. This so as not to run the risk of increasing latency in accesses, and of some functionality not working, due to being developed yet.
Read full review BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are
Microsoft SQL Server . Another benefit is that the monitoring job is easy to set up and centralize with other .NET application monitoring jobs.
Read full review Return on Investment ROI is negative, you need either to hire them to work with you or spend days/weeks to figure out issues. For some of the projects in the end it is not worth it, it is just a "buzz" to use serverless but not practical. Service is easy to set up authorization and it is easy to manage. Read full review A positive impact has been the quicker turnaround time of a part request and that part showing up in SAP using Biztalk as middleware. A somewhat negative impact has been the somewhat insufficient error logging/message capture settings that Biztalk provide. This has caused occasional delays when attempted to create parts for the business. A somewhat negative impact has been the need to have a specialized developer who understands Biztalk to troubleshoot issues with the Biztalk and SAP interaction when creating parts, and when adding new fields to the parts. Read full review ScreenShots