Built Good Enough: Why Small Firms Don't Need Enterprise Architecture

A small operation with around fifty employees wants to improve its order tracking. An external IT provider designs a state-of-the-art distributed architecture for it: a cluster of many small services, real-time queues, data storage across several regions. A year later, the company spends more time maintaining its server configurations than shipping its actual products. The technology was supposed to help and has become the main problem.

The pattern

The culture of software development is heavily shaped by the big technology corporations. Their architectures are built to serve billions of users worldwide — and for exactly that they're brilliant. But for a specialized mid-sized manufacturer, simply copying that way of building is a real mistake.

Highly complex distributed architectures bring an enormous configuration effort, demand elaborate debugging across networks, and cause permanently high maintenance costs. Each of these points is justified for a global service and pure burden for a 50-person operation. The technology solves problems this company simply doesn't have, and creates new ones in return that it didn't know before.

What a lean operation actually needs is the opposite of the trend: a manageable, reliable, and easily maintainable data structure — an architecture explicitly tailored to the real size and team strength. It isn't the most impressive solution that wins but the one that fits the company's scale.

From our practice

As a small core team, we design architectures consistently for long-term simplicity in operation. We deliberately build unspectacular, heavily consolidated systems — on robust databases proven over years and with clear, cohesive code structures wherever that's possible. "Boring" is a compliment to us, because boring systems rarely call at night.

Our yardstick here is a single question: can this system be fully operated, maintained, and extended by a single internal IT person with solid fundamentals? If yes, we've built it right. If it would take a specialized team the operation doesn't even have, we've engineered past the need.

That's why we measure the quality of our technical designs not by their sophistication but by how invisible and low-maintenance they stay over years of continuous operation. A system no one talks about anymore because it just runs is the best result we can deliver.

How to spot an oversized design

If you have an architecture proposal in front of you, a few sober questions reveal whether it fits your size:

• Does running this system need more people than the operation even has?
• Does the architecture solve a scaling problem you'll realistically never have?
• Can a single person understand the whole thing and repair it in an emergency?
• Does the team spend more time on the infrastructure than on the actual work?

If any one of these answers points the wrong way, the design isn't too modern but simply too big for you.

Takeaway

Good architecture isn't the one that can do the most but the one that fits your actual size and runs without complaint for years. For a mid-sized operation, a solid, maintainable, consolidated system is almost always the smarter choice than the corporations' distributed toolkit. If you're facing an oversized proposal, or a system already demands more upkeep than it delivers in value, we're happy to look together at what really holds up for your size.