I've seen this methodology used many times over. In
small scale shops, this can work fairly well where
enterprise level solutions are too costly when weighed
against their benefit.
However, when an in-house (or customized open source)
solution is used, more often than not, that business
then becomes dependent on the small group of
individuals that built the software. If they get hit
by the proverbial bus, the company is now up the creek
without a paddle. And because it's custom, you can't
just hire a consultant to jump in and take over.
That's just referring maintainability and not even
scalability/extensibility. Say you have a spike in
demand for your service, or you need a new feature,
are your techs able to drop everything they're doing
and add this in?
The point of centralizing, is that a 100% load
increase to you is probably 1% to your service
provider. They can spread the load out and account
for the unexpected.
Are you gonna put up an extra wind turbine, just
because the microwave is extra popular today?
Discussion on:
Message 2 of 1
IBM Sponsored Resources
Resources from our Sponsor
- Oracle Exadata vs IBM: Netezza Compared
- Forrester TEI Report
- CIA Whitepaper
- Harnessing the Power of Advanced Analytics
- Tapping into Unleashed Business Potential with Advanced Analytics
- Unlock Analytic Performance with Revolution R for Enterprise and IBM: Netezza Data Warehouse Appliance
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox




