Why Art2link ESB

The problem

Connect two systems and you write one interface. Connect five that all need to talk and you are maintaining twenty. Every new system multiplies the work, every format change breaks something, and nobody can answer "where is that message right now?"

That is point-to-point integration. It fails exactly when the business grows.

The fix: a bus

An Enterprise Service Bus (ESB) replaces the tangle with one central exchange. Systems never talk to each other. They talk to the bus.

Every integration on Art2link ESB runs the same simple three-step exchange:

1. Publish. A receive port takes a message from a source system and puts it on the bus.
2. Select. Send ports have subscriptions. Every subscription that matches the message selects it.
3. Deliver. Each matching send port transforms the message into its destination's format and delivers it.

One message in, any number of deliveries out. The sender never knows who is listening. Adding a destination means adding a subscription, not touching existing code.

What Art2link ESB is

Art2link ESB, by Cerebrum City, is an Azure-native enterprise service bus. Connectivity, routing, transformation, and guaranteed delivery, all as a managed platform. No servers to patch, no database to administer.

And you can try it today: every edition is available in the Azure Marketplace and installs automatically in under 30 minutes, and the Starter edition is license free.

The five refusals

The platform was built around a manifesto: five things its creators refused to carry forward from years of painful integration work.

1. No IDE. Everything, including C# code, is authored in the portal. Visual Studio never opens.
2. No compiling. The platform is 100% configurable. Even C# pipeline components and custom functions (NuGet packages included) are saved and run, never built.
3. No deploy gap. What you save is what runs, the moment you save it. No deployment-night surprises.
4. No restarts. Changes go live without restarting anything. Zero downtime.
5. No forced coupling. Loose by default, tight by choice. More on this in Module 2.

The BizTalk connection

If you know BizTalk Server, this model is familiar on purpose: receive ports publish, subscriptions select, send ports deliver. Art2link ESB keeps that pattern and removes what aged badly, starting with the SQL Server MessageBox. With BizTalk's paid extended support ending April 9, 2030, that is the migration the platform was built for.

Check yourself

Three quick questions on this module, in the same style as the exam. Not graded, not recorded, just practice with instant explanations.

Go deeper

• The Art2link Manifesto
• Architecture
• Migrating from BizTalk