Skip to content

Migrating off Microsoft BizTalk to Peregrine Connect

Migrate to Peregrine. It’s faster, easier and more cost effective than BizTalk.

Peregrine Connect is designed by .NET developers
to do what BizTalk Server never could

Not even Microsoft’s own BizTalk Server can compete with the .NET simplicity of Peregrine integration. Built by and for .NET developers, Peregrine Connect
offers a highly intuitive and easy-to-use interface that effectively and efficiently extends the .NET platform to provide real-time
reliable and durable messaging, application integration, business processing, and web service management.

Made to grow

Peregrine’s architecture is designed for more effective
request-response, low latency and high
throughput integration scenarios.

Built for speed

Peregrine compiles business processes and workflows
at time of execution to save you considerable
development time compared to BizTalk Server.

Designed to save

A recent comparison revealed that a Peregrine-based
solution required 30 fewer CPUs and 7 fewer servers
than a BizTalk Server-based solution.

Challenge

I need a modern integration solution that scales faster than BizTalk Server but won’t blow up my bottom line. Is there a simple way to migrate off of BizTalk Server?

BizTalk Server’s MessageBox persistent architecture puts a drag on scalability and performance. And the number of CPUs required to reach the performance envelope of modern distributed applications makes BizTalk a costly integration option.

Solution

Peregrine Connect - reliable and durable messaging, application integration, and web service capabilities are built to grow with your business. Make the migration to Peregrine today.

  • Build flexible solutions that adapt to your needs
  • Test and debug while you design
  • Reduce hardware and licensing costs

Challenge

I need a modern integration solution that scales faster than BizTalk Server but won’t blow up my bottom line. Is there a simple way to migrate off of BizTalk Server?

BizTalk Server’s MessageBox persistent architecture puts a drag on scalability and performance. And the number of CPUs required to reach the performance envelope of modern distributed applications makes BizTalk a costly integration option.


Solution

Peregrine’s reliable and durable messaging, application integration, and web service capabilities are built to grow with your business. Make the migration to Peregrine today.

Build flexible solutions that adapt to your needs

Peregrine is designed for request-response, low latency and high throughput integration scenarios that BizTalk Server is not equipped to handle effectively.

Peregrine’s application architecture features an optional stateless business processing environment that reduces latency and increases concurrency through asynchronous configuration options. And Peregrine doesn’t need a MessageBox-like database in the middle of message interaction or service orchestration, which further reduces latency while increasing concurrency.

Test and debug while you design

You won’t need to compile and deploy Peregrine business processes and workflows for testing. Peregrine’s Business Process and Workflow Designers support in-place testing, simulation and debugging, so you can run test messages through processes and workflows directly in the designer.

Peregrine’s built-in .NET debugger lets you set breakpoints to enable easy step-by-step debugging through both activities and custom programming code. And because Peregrine compiles business processes and workflows at time of execution, you’ll save considerable development time compared to BizTalk Server.

Reduce hardware and licensing costs

A recent comparison study revealed that replacing an actual BizTalk solution with Peregrine helped:

  • Reduce software licensing costs by 12x
  • Reduce annual support costs by 20x
  • Improve overall solution performance 
  • Streamline solution maintenance
  • Reduce solution implementation costs

The Peregrine-based solution was approximately 8.5x faster than the BizTalk Server-based solution. The existing BizTalk solution required 8 BizTalk servers with 32 total CPUs, and 2 SQL Servers with 8 CPUs. While Peregrine required only 1 Peregrine server with 2 CPUs, and 1 SQL Server with 2 CPUs.

ap-logo

“With no formal training, our own .NET development staff became proficient
with Peregrine in a very short period of time. This significantly eased
adoption, and reduced time and cost to deliver HD services.”

— Alan Wintroub, Director of Software Engineering, Associated Press

Read more about Peregrine Connect

Articles

Rabbit MQ Topics

Introduction Due to the open-source nature of RabbitMQ and constant updates, it is very hard for developers to master its…

Read More >>
White Papers

The Integration Journey to Digital Transformation with Peregrine Connect

The Integration Journey to Digital Transformation with Peregrine Connect

Read More >>
Case Studies

Elektro Gorenjska

Peregrine Connect Eliminates Over 30% of Point-to-Point Integrations and reduces development time by 90%

Read More >>
Videos & Webinars

Decision Test Data Mapping

– Use decisions to drive the execution of transformation logic – Chain a series of decisions to address complex scenarios …

Read More >>