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

Composable Architecture: Designing Modular Systems for Flexibility and Speed

August, 2022 — 7 min read

Introduction

As digital transformation accelerates in 2022, organizations face constant pressure to adapt their systems, processes, and products. Monolithic platforms often fail to meet this need for agility. That’s why composable architecture — the practice of building systems from independent, interchangeable modules — has gained serious traction. It allows enterprises to innovate faster, scale efficiently, and react to change with precision.

What Is Composable Architecture?

Composable architecture is a design paradigm focused on assembling systems from well-defined, loosely coupled components. These components can be services, APIs, UI blocks, or infrastructure modules. The goal is to create a system where each piece is independently developed, deployed, and replaced without impacting the whole. Composable architecture blends principles from microservices, headless systems, and modular design patterns.

Why Now?

Several factors make composable architecture especially relevant in 2022:

• API Maturity: REST, GraphQL, and event-driven APIs allow seamless integration across teams and vendors.
• Cloud-Native Tooling: Containerization, orchestration, and service meshes support independent lifecycle management.
• Business Agility: Product teams require autonomy to experiment and iterate without dependencies on central IT.
• Vendor Composability: Enterprises increasingly build ecosystems from best-of-breed services rather than single platforms.

Designing for Composability

To build a composable system, architects must make several strategic decisions:

• Define Clear Boundaries: Components should align with business capabilities and domains, not just technical layers.
• Expose Contracts: Every module must have a well-documented interface — typically via OpenAPI, AsyncAPI, or gRPC schemas.
• Abstract State: Avoid global state. Each component should manage its own data and expose state through APIs or events.
• Enable Discoverability: Use catalogs, registries, and developer portals to promote reuse and governance.

Composable Infrastructure and Operations

It’s not just about code. Platforms, pipelines, and environments must also support modularity:

• Infrastructure as Modules: Terraform modules, Helm charts, and Pulumi components should be treated as reusable primitives.
• Eventing Infrastructure: Use message buses, streaming platforms, and pub/sub systems to decouple communication flows.
• Composable Environments: CI/CD pipelines should dynamically assemble environments from component graphs.

Risks and Constraints

Composable architecture introduces new risks. Without strong governance, systems may become fragmented or inconsistent. Teams may reinvent capabilities or drift from shared standards. Observability and troubleshooting grow harder with more moving parts. Architects must balance autonomy with accountability — and establish guardrails for ownership, instrumentation, and SLAs.

Composable vs. Microservices

While microservices emphasize small, single-purpose services, composable architecture focuses on flexibility and recombination. Not every component needs to be tiny. Domain-aligned, product-focused modules are often more effective than overly granular services. The key is modularity with meaning, not fragmentation for its own sake.

Business Enablement Through Architecture

Composable systems allow business leaders to make changes without waiting on IT overhauls. A new payment gateway, a localized checkout flow, or an upgraded search engine can be plugged in with minimal disruption. Architecture becomes a lever for speed and differentiation — not a bottleneck.

Conclusion

Composable architecture enables organizations to design for change. In August 2022, this means building systems that are modular by intent, not just by accident. Architecture that is adaptable, observable, and discoverable unlocks real innovation. It’s no longer about building the perfect platform — it’s about building the platform that can evolve the fastest.

Eduardo Wnorowski is a systems architect, technologist, and Director.
With over 27 years of experience across enterprise infrastructure, networks, and cloud-native platforms, he helps organizations design resilient, scalable, and observable systems.
Eduardo blends deep technical expertise with strategic oversight, guiding teams through complex transformations and architectural challenges.
LinkedIn Profile