How Worktile Built a Scalable MEAN Stack with Real‑Time Messaging

Since its launch, Worktile has attracted more than 100,000 teams by offering a stable, user‑friendly collaboration tool. The system addresses four key technical challenges: cross‑platform web access, native‑like UI interactions, efficient real‑time messaging, and overall service stability.

SPA Design

Worktile adopts a single‑page application (SPA) architecture to minimize page navigation. After evaluating Backbone.js, the team chose AngularJS for its two‑way data binding, declarative syntax, modular design, and built‑in dependency injection, which together simplify UI updates and code organization.

Key AngularJS advantages highlighted:

Automatic two‑way data binding ensures UI reflects data changes instantly without manual DOM manipulation.

Semantic directives separate UI markup from business logic, allowing concise templates for components such as task lists.

Modular architecture enables each functional area (projects, tasks, schedules, files, topics, documents) to be developed as an independent module.

Dependency injection reduces coupling between modules, improving maintainability.

Although AngularJS has some drawbacks, its fit for Worktile’s needs proved effective, and the team notes the emergence of Angular 2.0 as a future consideration.

Service Design

The backend follows a MEAN stack (MongoDB, Express, AngularJS, Node.js) complemented by ejabberd for real‑time messaging.

API services (Web, Mobile, Open) run on Node.js, leveraging its asynchronous event‑driven model for high concurrency and enabling shared language across front‑ and back‑end.

Cache and queue layers use Redis, taking advantage of its in‑memory speed, persistence options, and pub/sub capabilities for loosely coupled data change notifications.

Database choice is MongoDB, offering high performance, easy clustering, and BSON storage that aligns naturally with Node.js.

File preview service provides in‑browser viewing of various file types. Text‑based files are rendered directly, while Office documents are handled via Microsoft Office Web App integration.

Message Push

Real‑time updates are critical for collaborative work. Worktile maintains long‑lived connections between clients and servers, pushing change notifications instantly. Initially, Socket.IO was used, but scaling challenges led to a migration to ejabberd (an Erlang‑based XMPP server) with Redis for presence storage and MongoDB for user data. The web client connects via Strophe.js using BOSH (long‑polling) due to limited WebSocket support in ejabberd.

Various push techniques considered include short polling, long polling, and WebSocket; the final architecture balances performance, scalability, and compatibility.

Conclusion

Worktile’s architecture exemplifies a classic MEAN stack augmented by XMPP‑based real‑time messaging. Teams should select technologies that match their product requirements and team expertise.