Skip to content
Search

Zod.kr

lastmod 2025-03-14created 2025-03-142 edits

A community for computer hardware and mobile enthusiasts, experts, and gamers, and a webzine specializing in technical analysis.

An IT community in South Korea. The YouTuber Ppeoljit Yeonguso joined as part of the operating staff.

zod.kr after 4 months of development and 2 months of operation - servers and services

A post about the tech stack chosen and the development process while building a Korean community site (zod.kr).

With 10x the expected traffic coming in due to a major blunder by a competing site, the server crashed and was restored. A resource diet to optimize traffic costs.

INFORMATION

The following is a summary made with Grok 3.

Shares the experience of developing the IT community zod.kr as a solo developer. Includes the optimization process to cut server costs.

  • Background: returned to web development after 3 years and to PHP development after 7 years. Switched to full-stack development.
  • Service stack: Rhymix(CMS), Oracle Cloud Free Tier (initially), Cloudflare (security), Bunny.net (CDN), Naver Cloud (email).
  • Initial server: Oracle Free Tier (24GB RAM, 4-core ARM, 150GB storage). Chosen for its 4TB of free traffic, but after launch, unexpected 10x traffic caused network drive disconnections and a server collapse.
  • Server migration: emergency move to Vultr. Temporary reopening after 30 hours of work without sleep.
  • Traffic problem:
    • Cloudflare Argo ($0.1 per GB) cost $20 a day, projected at 1,000,000 won per month.
    • Switched to Bunny.net, cutting costs to 15–20% of that.
    • 27,000–30,000 daily visitors; keenly felt the need for traffic optimization.
  • Optimization efforts:
    • Reduced the size of icons (Iconoir) and web fonts (Pretendard).
    • Minimized inline scripts/styles, removed HTML comments.
    • Applied lazyload to reduce Bunny.net traffic (6888GB → 4446GB).
    • Saved 3–4GB by blocking bots and introducing an API whitelist.
  • Results:
    • Cloudflare peak traffic 211GB → 12GB, total traffic down 57%.
    • Costs cut by 70–80% ($26 → $3.48 per day).
  • Lesson: Cloudflare is beneficial when used well and poison when used badly. Realized the importance of traffic management.

See also

  • IT community

Favorite site

author Zer0 sitemap