Integration #FAIL – Part 2: Lying in the path of an oncoming bus

Rhianna RichardsRhianna Richards is a copywriter and editor based in San Francisco. She spends most of her time simplifying the complex and writing about the crazy world of enterprise tech. With what’s left, she tries to figure out why. Formerly in high-tech PR, she has extensive experience in corporate communication strategy and always encourages the proper use of grammar.

Point-to-point integration can be a quick fix for getting information from system to system. All it takes is a bit of code and voilà – connection complete!

But what happens when the programmer who wrote the script falls off the face of the planet? Inevitably, a change will be submitted by the business. Just how long will it take to find the keys that unlock the black box?

A single instance might be manageable but if you’re like most organizations, dozens of hard-coded, point-to-point interfaces run beneath the surface of application development projects.

And chances are, developers used different technologies over the years, making it difficult to know where issues lie, let alone what could be causing a problem.

It could take an army to overcome a situation like this on a larger scale, not to mention escalated cost. So the question becomes: how much of your business’ agility and resources are you willing to put at risk?

  • Remain Open: Standard interfaces (which remove logic from the application layer) will enable you to expose the business functionality of applications much more easily without having to understand the complexity of integration logic.
  • Keep it Simple: Model-driven interfaces (EDI) providing visibility into application logic will give you a clear understanding of connectivity between your systems and applications. Model-driven interfaces also make it easier to incorporate or remove components, increasing flexibility of the architecture overall.
  • Get on the Bus (not under it): Leveraging a bus-based architecture, you can manage connections with applications through one interface. And when the time comes for inevitable system upgrades, you have only have one interface to maintain…one that scales more easily and delivers higher availability.
While point-to-point may seem efficient in a pinch, it has long-term risk for the organization and becomes a bad habit. By remaining open, keeping it simple and getting on the information bus, you will lower your “bus risk” and future-proof your organization in the process.
This article was first published on The TIBCO Blog and has been lightly edited.

Tags: ,

Categories: Information Technology, Infrastructure, SOA / B2B

Author:Jeanne Roué-Taylor

I'm fascinated by disruptive technology and its impact on our world. I manage sales operations for an excellent startup with a unique team of highly experienced data scientists.

Subscribe to the blog

Subscribe and receive an email when new articles are published

No comments yet.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: