Securely connects distributed apps and services across public cloud, on-premises, and edge environments. Utilizing Infrastructure as Code, App Connect provisions resources and maintain uniform policies across multiple sites.
My advice is if your firm build multi-cloud, high availability SaaS products or you just run polyglot workloads across kubernetes and VMs, then F5 Distributed Cloud App Connect is your guy. Coming from an expert, just start with a few core services or else you will be overwhelmed.
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.
Ease of use - standing up a new site took very little time, less then an hour.
Connecting the dots - the ease at standing up a load balancer and advertising it on CEs was simple and straight forward. Once you get familiar with the field layout it's very comparable to BIG-IP
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.
At this point it has become too focal to our operations. An entire department could collapse if we dropped it now or in the near future. My experiences as mentioned in the previous questions tell of its gravity
From what we have been able to test load/responsiveness is quick and when we've tested out reporting and troubleshooting modules they have pulled the correct information in quick timeframes. We haven't been able to test out any software integration with Splunk of other software on our system since we are still in early POC stages but from what we've been told we should be able to implement that in our environment
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.
-F5 Distributed Cloud App Connect provides more granular security policies with features like DOS, WAF etc and others lack -F5 Distributed Cloud App Connect provides high performance global network and other rely on public internet and impact is latency and it gives F5 Distributed Cloud App Connect a better user experience
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.
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.
