|By Hollis Tibbetts||
|November 11, 2011 09:00 AM EST||
The More Things Change, the More They Stay the Same
I remember back in the mid/late 1980's talking to IT departments about the concept of a relational database, and why having one on their VAX would be a good idea.
In many cases, my recommendation was met with some head scratching, brow furrowing and comments along the lines of "why would be buy one of those, when we can just build our own data storage system using RMS records?"
100 years later, it's a pretty rare occurrence that someone would decide to build their own data storage and manipulation system - if they do, it's because of some unusual requirement. As far as I know, nobody considers "build" as the default strategy in this area.
Integration - the Debate Still Continues
The build vs. buy debate still rages on when it comes to data or application integration, though. I've lost count of the conversations I've had that include phrases like "it's just a few Web Services" or "the API is easy to write to" or "it's just a simple point-to-point integration".
If you want to hire me to evaluate your situation and make a recommendation on whether you should build your own integration "mechanism" or just buy one, that's great - be forewarned that 994 times out of 1000, the answer will be "go buy one".
Oh, and the remaining 6? 5 will be "could go either way" (which means "buy") and only 1 would be "build is better for you".
Why Is Hand-Coding (Almost Always) a Bad Idea?
There are a lot of reasons, but they pretty much boil down to:
1) Integration is much more complicated than people think
2) Management and "Error Recovery" is complicated
3) Changing applications, data sources and APIs are an issue
4) Performance can be an issue
5) Maintenance and enhancement is expensive
6) Scalability to additional data sources/targets is a challenge.
Why Even Simple Integration Costs over $100,000 to Code and 11 Questions to Ponder
I've written a more comprehensive article on ebizQ's Integration Edge - including a list of 11 questions to consider before building your own integration.
- ARM Server to Transform #BigData to #IoT | @CloudExpo #DigitalTransformation
- Software Quality Best Practices: Healthy Software
- Twenty-Thousand Men Pregnant Because of Bad Data
- $3 Trillion Problem: Three Best Practices for Today's Dirty Data Pandemic
- Question: Why Is IT Project Failure Always an Option?
- Why Infrastructure Technology Is Challenging
- Modernization of IT: Solving a Legacy of Business Problems & Applications
- Flourishing ARM Server Market Creates Opportunity – for Software
- Legacy Modernization
- Klout Crisis Leads to Tough Questions for PROskore Founder Bill Jula