Building a Niche Social Network: from MVP to Scalable Platform

We create turnkey social networks. In over 10 years, we've burned our fingers on realtime notifications, feeds, and moderation. The typical problem: the client wants 'like VKontakte' but forgets about the N+1 issue in the feed and hydration. We'll tell you how to avoid the rake.

Any social network starts with a social graph. Its architecture determines the performance of the activity feed, notifications, and even recommendations. An incorrectly chosen feed model (push vs. pull) leads to degradation as users grow. We use a hybrid model, adapting to the load.

Recently, we launched a niche social network for a professional community of designers — 300,000 users, 5 million posts per month. The main pain point: the feed lagged under peak load. We solved it by redesigning the graph and implementing a hybrid feed. Result: LCP dropped from 4 to 1.8 seconds, and server load halved. In another project, a bug in the feed algorithm caused a loss of 30% of the active audience; the incident cost $20,000 per day. After refactoring the feed, we saved $8,000 per month on server infrastructure. The right graph architecture helps avoid such losses.

Social Graph: How to Avoid N+1?

Two types of relations: symmetric (friendship) and asymmetric (subscription). Storing the graph in a relational database:

CREATE TABLE follows ( follower_id BIGINT REFERENCES users(id), following_id BIGINT REFERENCES users(id), created_at TIMESTAMP, PRIMARY KEY (follower_id, following_id) ); CREATE INDEX ON follows (following_id); -- query "who follows X" 

For large user bases (>10M), it's better to store the graph in specialized graph DBs (Neo4j, Amazon Neptune) or Redis with SSCAN. Facebook Engineering recommends a hybrid feed model precisely for this reason.

Why Hybrid Feed is the Industry Standard?

Fan-out on write (push): fast write, but a million followers means a million writes. Fan-out on read (pull): saves space, but slower. We use a hybrid: push for regular users, pull for popular ones (threshold >5000 followers). This is standard for Facebook and Instagram. Additionally, ranking (algorithmic feed) takes into account likes, comments, reposts, and author proximity.

# Redis ZSET for user feed ZADD feed:{user_id} {timestamp} {post_id} ZREVRANGE feed:{user_id} 0 19 -- last 20 posts 

See Redis Sorted Sets documentation.

How We Solve Realtime?

For the feed we use ZSET, for realtime chat — Pub/Sub. Without Redis, each WebSocket server would store state, and connections would break on failure. Redis solves this: any server publishes an event to a channel, all servers with WebSocket connections receive it and deliver to subscribers.

Media Storage and Processing

Photos and videos go into object storage (S3/Cloudflare R2). Processing:

• Photos: resize → multiple thumbnails (150, 400, 800px) → WebP conversion
• Videos: transcoding via FFmpeg or cloud (Cloudflare Stream, Mux)

Processing is asynchronous via a queue. The user sees 'processing', then gets a notification when ready.

Content Moderation: from Hash Filtering to ML

• Hash filtering: PhotoDNA / PDQ hash for detecting known CSAM and illegal content
• ML moderation: NSFW image detection (Google Vision Safe Search API, NudeNet)
• Text moderation: toxicity detection (Perspective API, OpenAI Moderation API)
• User reports → queue for moderators → decision (remove/keep/warn)

Stages of Social Network Development

1. Requirements analysis and graph design: define relation types, feed model, realtime functionality.
2. UI/UX prototyping: create wireframes and a design system optimized for mobile.
3. MVP development: profiles, subscriptions, photo posts, comments, activity feed, basic notifications.
4. Integration of realtime chat and media processing: WebSocket + Redis Pub/Sub, video transcoding, WebP for photos.
5. Implementation of moderation and privacy: hash filtering, ML detection, privacy settings, GDPR.
6. Testing, deployment, and optimization: load testing, CI/CD, LCP/CLS monitoring.

Privacy and GDPR

Timelines and Cost

Cost is determined individually based on functionality and scale. We guarantee transparent pricing and no hidden fees.

What's Included in the Work

• Architecture documentation (ERD, flow diagrams)
• Access to repository, CI/CD, object storage
• Training for your team (2-3 sessions)
• 6-month warranty support after launch

Feed Model Comparison

We build scalable social platforms ready for growth. Contact us for a consultation on your social network architecture. Order an MVP development today — we'll assess your project for free.