Chatmod
Technology Radar
- Nestjs
- MongoDB
- Mongoose
- Socket.IO
- React
- Tailwind CSS
- Clerk Auth
- React Native
The Challenge
Traditional religious and community platforms rely heavily on fragmented communication channels, static websites for calendars, WhatsApp for groups, and email for announcements. This disorganization causes information loss, low mid-week engagement, and excludes members who prefer a unified, modern digital space. The technical hurdle was scaling real-time message rooms alongside a flexible, highly performant timeline feed that handles multiple distinct content structures.
Fig 1. User Interaction Flow
The Solution
I engineered a centralized, data-driven platform using a FeedItem Aggregation Model. By abstracting posts, events, devotions, and announcements into a single polymorphic schema in MongoDB, the application serves a fast, paginated timeline with zero heavy database joins. Socket.IO handles instantaneous data broadcasting across direct messages and ministry channels, while Clerk safely handles identity federation and user sync to keep local account records pristine
Unified Feed Architecture: Aggregates posts, events, and devotions into a single timeline stream.
Real-Time Mesh: Bi-directional Socket.IO connection for chat, unread counts, and active feeds.
Sub-Community Layer: Isolated spaces for specific groups (Youth, Choir, Media Teams) with custom feeds.
Spiritual Devotional Engine: Tools for creating, targeting, and interacting with faith-focused content.
Synchronized Identity: Clerk webhooks securely match cloud authentication with local database models.
Dynamic Event Organizer: Real-time scheduling, tracking, and countdown components for community programs.