Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

"At a large scale, it starts to be pretty difficult to maneuver if each dept of 30-50 people has built or contracted all their own infra & services."

This is one of the biggest risks I've seen, for both large organizations and small ones.

Large organizations are built of small organizations, and a bunch of effective small organizations will each be moving and shaking, and building or buying things that become part of their infrastructure. Then one day you wake up and discover that your overall organization is paying for 27 different solutions to the same problem.

Then, any attempt to collapse that down to something reasonable results in zero productivity for quite a while and whole lot of pissed off people.



The question is, is it really worth it to collapse it down?


That depends on so many things.

One of the things I've seen cripple large organizations is waiting for the common infrastructure / services becoming mature enough to be used in production.

Teams are kept in a holding pattern, sometimes for years, while waiting for the teams to deliver their common infrastructure / services solutions, and they're actively discouraged from building their own solutions, because the enterprise-wide solution is "just around the corner".


Internal FUD?


It depends, but generally yes. Collapsing to 1 may or may not be a good thing, but you probably want less than 3-5 different DBMS, CMS, Cloud providers, printing services, source control systems, office supply/equipment, etc.


And suddenly I'm reminded of the web app I put together that needed three DB drivers...


At some level, absolutely. Your organizations aren't usually totally independent units - they need to interoperate with other organizations.

To the extent that the spaghetti of infrastructure prevents effective interop, that's a problem.

And as the need for interop grows between two orgs the cost of the various hacks, shims, and other cheap adaptations, escalates, until unification of infrastructure starts looking awwwwfully tempting.

Of course, unification comes with its own set of problems.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: