This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

ESBs: Standards-Based vs. Standardized

Stefan Tilkov,

Neal Ford on ESBs:

Having proprietary glue is not necessarily a bad thing. It's one of the factors you have to consider anytime you are thinking about turning part of your infrastructure over to a externally developed piece of software. Obviously, no one is going to build their own database server -- it makes good sense to buy an existing one, and fight the nasty battle if and when it comes time to move to another one. BUT, you need to understand the distinction between standards-based and standardized so that you don't buy yourself into a real long term nightmare.

I agree, except that I believe the ESB lock-in is much worse than a DB lock-in because (most) vendors want you to put their ESB in the very center of your company-wide architecture, whereas the DB is usually hidden behind the application's outer boundary (UI or interface).

Or at least it should be. Of course, you might be using your "ESB" to integrate DB access into process flows and dare to call it SOA instead of EAI.

On January 12, 2009 2:21 PM, Mark Griffin said:

“Of course, you might be using your “ESB” to integrate DB access into process flows and dare to call it SOA instead of EAI. “

Wouldn’t be EAI either, just integration. EAI done properly has no knowledge of source or target systems. EAI was designed to eliminate or reduce the tightly coupled enterprise. Of course EAI can and has been done badly leaving companies with a lot of brittle point to point interfaces. The same can be said for services in the SOA world as well. Loose coupling, agility, abstraction pre-date the current SOA definition and were in use in numerous other architectures including EAI. The main argument most enterprises used to bring in packaged EAI solutions was: loose coupling, agility, abstraction. They didn’t all do it right but as I said the same thing can be said about SOA.

As for vendor lock-in I have mixed feelings about that. Here is a post I just put out on it - . You can see from the post that I kind of go back and forth on whether lock-in is really an issue, call it rambling if you will. I for one would like to see more discussion on the practical issues around vendor lock-in and open-source solutions. Can your IT shop really take advantage of the open-source software? Does it really prevent lock-in?