Microsoft BizTalk Server is an on-premises integration server whose 2020 release is the last. Pages here cover the support deadlines and moving orchestrations, maps and messaging to Apache Camel with an open-source broker.
Comparing BizTalk Server with Apache Camel for on-premises enterprise integration: orchestrations against Camel routes, adapters against components, XSLT maps and schemas, message persistence, Windows and SQL Server licensing against a JVM stack, and skills.
Moving BizTalk applications to Camel: inventorying orchestrations, ports, pipelines and adapters, reusing XSD schemas and XSLT maps, replacing MessageBox routing with RabbitMQ or Kafka, re-creating tracking, and migrating in waves before mainstream support ends.
BizTalk Server 2020 is the last version, sales end in March 2027 and mainstream support in April 2028. This page compares Microsoft's path to Logic Apps Standard with moving to self-hosted Apache Camel, including paid extended coverage and what it excludes.
Cost of ownership by component: BizTalk, Windows Server and SQL Server licenses, HA and disaster recovery, specialist support and paid extended coverage, against Camel on your own servers or Kubernetes, a message broker, migration effort and operations.
The MessageBox is BizTalk's publish-subscribe core in SQL Server. This page covers replacing it with RabbitMQ exchanges or Apache Kafka topics, mapping subscriptions and correlation, guaranteed delivery and ordering, and what changes for monitoring.
Microsoft's successor, Logic Apps hybrid, is partially connected and needs outbound Azure access. For plants, utilities and government networks with no internet path, this page covers replacing BizTalk with Apache Camel and a broker that run fully offline.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.