Clikkle was expanding its Worksuite ecosystem with productivity and collaboration tools, but there was no centralized infrastructure for handling file storage and document management across products. Teams relied on disconnected systems that created fragmented workflows, duplicated files, inconsistent permissions, and poor collaboration experiences.

The objective was not simply to build a storage application, but to create a foundational product layer that other applications inside the ecosystem could depend on. Similar to how Google Drive integrates with Google Docs, Gmail, and Workspace tools, Clikkle Files was envisioned as the central file infrastructure connecting the ecosystem together.

The platform needed to be scalable from day one, capable of supporting future integrations, organization-level collaboration, increasing storage demands, and high-volume uploads without requiring major architectural rewrites later.

Traditional CRUD-based systems quickly became inefficient when nested folder hierarchies, permission inheritance, and large file uploads entered the picture. Uploading files through the backend created unnecessary memory overhead, while deep metadata traversal caused slow query performance and unstable scalability during testing.

Building organization-wide collaboration introduced challenges around role-based permissions, secure sharing, audit logging, and maintaining consistent access control across folders, files, and shared resources. The system needed to remain secure while still feeling simple and intuitive for end users.

The platform could not be optimized only for current requirements. It needed to support future ecosystem integrations, growing datasets, increasing user activity, and large-scale cloud storage demands while maintaining reliability, performance, and maintainability over time.

Create a cloud-native architecture capable of handling large file uploads, high-volume traffic, and organization-scale collaboration while remaining modular and easy to extend in the future.

Build a file management experience that feels fast, intuitive, and familiar despite the complexity of the underlying backend systems and permission structures.

Design the platform in a way that future Clikkle products could integrate seamlessly with the storage system without requiring significant infrastructure changes or duplicated logic.

Users could upload, organize, search, move, and manage files using nested folder structures with drag-and-drop interactions, bulk actions, optimized navigation, and metadata-based search capabilities designed for handling large datasets efficiently.

Implemented organization-based collaboration with granular role-based permissions including viewers, editors, and administrators. The platform also supported secure file sharing, version history tracking, and audit logs for improved accountability and transparency.

The infrastructure supported direct cloud uploads through AWS S3, intelligent frontend caching, optimized database querying, lazy loading, and scalable APIs designed to maintain responsiveness even during heavy file operations and large-scale usage.

PostgreSQL was used for relational consistency around users, organizations, authentication, and permissions, while MongoDB handled flexible file metadata and deeply nested folder structures more efficiently. This hybrid approach balanced scalability, flexibility, and maintainability.

Instead of routing uploads through the backend server, the system generated secure pre-signed AWS S3 URLs allowing files to upload directly to cloud storage. This significantly reduced backend overhead, improved upload stability for large files, and enabled better scalability.

TanStack Query handled caching, synchronization, and optimistic updates while Redux managed complex explorer interactions and global application state. Combined with Next.js rendering optimizations, this created a smooth and highly responsive user experience.

Next.js and React powered the user interface, handling file navigation, uploads, caching, optimistic updates, and real-time interaction flows while maintaining a responsive and intuitive experience across the application.

Express.js APIs handled authentication, metadata processing, permissions, and business logic orchestration, while AWS S3 managed scalable object storage using secure direct upload flows to minimize backend processing overhead.

The client first requested a secure upload URL from the backend, uploaded files directly to AWS S3, and then synchronized metadata into PostgreSQL and MongoDB. This separation improved scalability, reduced latency, and kept the system modular for future integrations.

Shared folders and organization-level collaboration introduced complex permission inheritance challenges where nested resources needed to remain secure, consistent, and performant. Middleware-driven access validation and structured permission mapping helped maintain scalability without sacrificing security.

Large datasets and metadata-heavy operations initially created slow rendering and retrieval times. Database indexing, optimized queries, frontend caching strategies, and lazy-loading approaches significantly improved application responsiveness during high-volume usage.

Since the platform was expected to support future ecosystem integrations, the architecture needed to remain modular and extensible from the beginning. This required careful planning around APIs, storage flow, database structure, and authentication consistency to avoid future technical debt.

Query optimization, frontend caching, and metadata restructuring reduced file retrieval latency by approximately 45%, while AWS S3 direct uploads lowered backend processing overhead by nearly 60%, resulting in a significantly faster and more scalable platform.

The platform successfully centralized file management workflows inside the Clikkle ecosystem, improved collaboration capabilities, reduced infrastructure bottlenecks, and created a scalable storage layer that future products could integrate with seamlessly.

Leading the project independently strengthened my expertise across frontend engineering, backend architecture, cloud infrastructure, DevOps, database optimization, and system design. The experience reinforced how important scalability, performance, and thoughtful architecture are when building production-grade applications.