The Return of Thick Clients: Architecture Reimagined for Modern Needs

September 2023 · Reading time: 6 min

The computing pendulum swings again. For years, organizations migrated to thin clients and web-based apps, chasing centralized control, security, and simplicity. But in 2023, the architectural tide turns as thick clients quietly return to relevance. This shift isn’t nostalgia—it’s a strategic evolution, driven by modern edge workloads, disconnected operations, and performance demands that the cloud alone can’t meet.

What’s Driving the Resurgence?

Thick clients—or rich clients—are applications that execute most processing locally while communicating intermittently or selectively with back-end systems. Unlike traditional fat clients of the 1990s, today’s versions are security-hardened, modular, and often containerized. Several factors contribute to their revival:

• Edge Computing: Devices at the edge (in factories, clinics, or retail) require robust local functionality due to latency and bandwidth constraints.
• Offline Tolerance: Field teams in rural or high-security environments need systems that remain functional without constant connectivity.
• Resource Availability: Modern laptops and mobile devices are highly capable, rendering cloud-only designs underutilized and frustrating.
• Developer Tools: Frameworks like Electron, Flutter, and .NET MAUI allow building cross-platform thick clients efficiently.

Architectural Implications

The reintroduction of thick clients forces a reevaluation of systems architecture:

• Synchronization Models: Data consistency between the local client and the central system becomes a core design concern. Patterns like CRDTs and conflict resolution strategies matter more than ever.
• Security Boundaries: Modern thick clients must assume hostile environments and enforce robust encryption, secure storage, and fine-grained access control.
• Update Strategies: Code and content must be updatable without complete reinstalls. This often means building in remote patching or self-updating mechanisms.
• Data Responsibility: Local persistence introduces data lifecycle concerns: retention, compliance, audit trails, and more.

When Not to Use Thick Clients

This trend doesn’t signal the demise of thin clients. Web apps remain ideal for certain workloads, especially where rapid iteration, limited local resources, or ubiquitous access are paramount. For simple CRUD applications with minimal UI complexity, web-first remains the superior choice.

Design Considerations in 2023

Teams returning to thick client paradigms must internalize lessons learned since the 2000s. Key recommendations:

• Adopt declarative UIs and test automation from the start to ensure quality and maintainability.
• Separate local data storage from logic to facilitate syncing and modularity.
• Employ secure by design practices—assume compromise, validate everything, and reduce privileges.
• Instrument local apps for diagnostics, logging, and update tracing.

Not a Regression—A Rebalancing

The return of thick clients is not a rejection of the cloud—it’s a recalibration. Architecture must serve users and use cases. In a world of drone inspections, remote medicine, and intermittent connectivity, thick clients provide continuity, performance, and agency at the edge.

As always, smart architecture acknowledges trade-offs and finds balance between local capability and centralized oversight. For many organizations, embracing hybrid architectures that include thick clients is a strategic step forward.

Eduardo Wnorowski is a Technologist and Director.
With over 30 years of experience in IT and consulting, he helps organizations maintain stable and secure environments through proactive auditing, optimization, and strategic guidance.
LinkedIn Profile