<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[TVNOON – Sports Tech & Development]]></title><description><![CDATA[TVNOON – Sports Tech & Development]]></description><link>https://tvnoon.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Sun, 22 Nov 2026 17:12:19 GMT</lastBuildDate><atom:link href="https://tvnoon.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How I Built TVNOON with Node.js 22, Express 5, and SQLite]]></title><description><![CDATA[눈팅티비(TVNOON)를 Node.js 22, Express 5, SQLite로 개발한 과정입니다. 스포츠중계·해외스포츠중계·실시간중계 정보와 WebRTC 연결 구조를 소개합니다.]]></description><link>https://tvnoon.hashnode.dev/tvnoon-nodejs22-express5-sqlite-webrtc</link><guid isPermaLink="true">https://tvnoon.hashnode.dev/tvnoon-nodejs22-express5-sqlite-webrtc</guid><category><![CDATA[Node.js]]></category><category><![CDATA[Express JS]]></category><category><![CDATA[SQLite]]></category><category><![CDATA[WebRTC]]></category><category><![CDATA[Web Development]]></category><dc:creator><![CDATA[최진호]]></dc:creator><pubDate>Tue, 17 Nov 2026 09:42:06 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6afc1e04ed12bf99646c5a8e/7b145f5b-337f-4709-ab00-5eda3182f8e1.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Building a modern sports streaming information platform involves more than displaying match schedules or providing access to sporting events. It requires an architecture capable of organizing frequently changing information, delivering web pages efficiently, and integrating external streaming technologies without unnecessary infrastructure complexity.</p>
<p>As an independent web developer, I created TVNOON (눈팅티비), a sports-focused web platform designed to bring together live sports information, international match schedules, and streaming-related resources.</p>
<p>The project was inspired by the growing demand for accessible sports information, particularly among users interested in 스포츠중계 (sports streaming), 해외스포츠중계 (international sports streaming), and 실시간중계 (live streaming).</p>
<p>Rather than developing a complicated system with multiple frontend frameworks and independent media servers, I decided to approach the project differently.</p>
<p>I built TVNOON using Node.js 22, Express 5, and the built-in SQLite database available in Node.js. The application uses server-generated HTML, while external WebRTC providers handle video delivery directly to the user's browser.</p>
<p>This article explains why I chose this architecture, how the different components work together, and what I've learned while developing TVNOON.</p>
<h2>1. The Inspiration Behind TVNOON</h2>
<p>Sports fans today follow more competitions than ever before.</p>
<p>Football enthusiasts watch international leagues and tournaments, basketball fans follow domestic and overseas competitions, and baseball audiences regularly check match schedules across different time zones.</p>
<p>Finding relevant information isn't always convenient.</p>
<p>Users may need to visit multiple websites to discover upcoming matches, check available streaming information, or learn more about their favorite sporting events.</p>
<p>In South Korea, search terms such as 스포츠중계, 무료스포츠중계 (free sports streaming), and 해외스포츠중계 reflect different ways sports fans look for live events and viewing information.</p>
<p>These search interests helped me think about the information architecture of TVNOON.</p>
<p>Some visitors want to discover which matches are taking place today. Others are primarily interested in international football, basketball, or baseball.</p>
<p>There are also users searching for 실시간중계 because they want timely information about sporting events currently taking place.</p>
<p>My goal was to build a platform that organizes these different information needs within a consistent and accessible web experience.</p>
<p>I wanted TVNOON to be straightforward to navigate, practical to maintain, and flexible enough to evolve as new requirements emerge.</p>
<h2>2. Choosing a Lightweight Technology Stack</h2>
<p>One of my earliest decisions was to avoid adding technologies simply because they were popular.</p>
<p>A sports information platform needs reliable request handling, structured data storage, efficient HTML delivery, and a way to keep match listings updated.</p>
<p>These requirements don't automatically justify a large frontend framework or a microservices architecture.</p>
<p>For TVNOON, I selected three core backend technologies.</p>
<h3>Node.js 22</h3>
<p>Node.js 22 provides the runtime environment for the application.</p>
<p>I use it to execute the server-side JavaScript responsible for handling application logic, processing requests, and retrieving sports event information.</p>
<p>Node.js is particularly useful for applications that interact with external services and handle frequent network operations.</p>
<p>Its asynchronous programming model provides a practical foundation for retrieving match listings while continuing to serve web requests.</p>
<h3>Express 5</h3>
<p>Express 5 handles HTTP routing and the application's web request lifecycle.</p>
<p>I chose Express because it allows me to build a straightforward server architecture without adopting a much larger application framework.</p>
<p>The application generates complete HTML pages on the server and delivers those pages directly to visitors.</p>
<p>Express gives me control over routing, response handling, and how content is presented.</p>
<h3>Built-in SQLite</h3>
<p>TVNOON uses the SQLite functionality included with Node.js rather than depending on a separately deployed database server.</p>
<p>SQLite provides relational data storage while keeping infrastructure requirements relatively simple.</p>
<p>This architecture reduces the number of independent services I need to manage.</p>
<p>It also encourages me to think carefully about database operations, write patterns, and how information should be organized.</p>
<p>SQLite isn't necessarily the correct choice for every high-traffic application, but it is a practical option for projects where a compact architecture and straightforward deployment are important.</p>
<h2>3. Why I Chose Server-Side HTML Instead of React or Vue</h2>
<p>One of the defining characteristics of TVNOON is that it doesn't use a frontend JavaScript framework.</p>
<p>Instead of building the interface around React, Vue, or a similar framework, the Express application returns complete HTML documents.</p>
<p>This approach is based on server-side rendering.</p>
<p>The request flow is straightforward:</p>
<p><strong>User's Browser → Express Server → Generated HTML → Browser</strong></p>
<p>When someone visits a TVNOON page, the server processes the request and returns the HTML needed to display that page.</p>
<p>This choice was influenced by the type of information the platform presents.</p>
<p>Sports schedules, event listings, and related content benefit from a clear page structure and accessible navigation.</p>
<p>A server-rendered architecture lets me maintain direct control over the initial content without introducing an additional frontend build system.</p>
<p>It also allows the application to deliver meaningful HTML before any optional browser-side interactions occur.</p>
<p>This can support search-engine accessibility, although actual indexing and rankings still depend on content quality, technical configuration, and search-engine behavior.</p>
<p>For a project like 눈팅티비, where discoverability and content organization are important, I consider this a useful architectural characteristic.</p>
<p>Of course, server-side rendering doesn't eliminate the need for good frontend development.</p>
<p>Responsive layouts, accessibility, browser compatibility, and efficient resource loading still matter.</p>
<p>The important point is that I can address those requirements without making a frontend framework a mandatory part of the application.</p>
<h2>4. Keeping Sports Match Listings Updated Every 30 Seconds</h2>
<p>Sports information changes throughout the day.</p>
<p>An upcoming football match becomes a live event. A basketball game finishes. New matches appear on schedules as competitions progress.</p>
<p>For a platform focused on 스포츠중계 and international sporting events, keeping match listings reasonably current is an important requirement.</p>
<p>However, I wanted to avoid an architecture in which every visitor independently triggered the same external data requests.</p>
<p>My solution was to make the application server retrieve updated sports match listings every 30 seconds.</p>
<p>The basic workflow is:</p>
<ol>
<li>The TVNOON application server requests updated match listings from its external data source.</li>
<li>The server processes the retrieved information for use within the application.</li>
<li>Visitors access sports listings through the website's normal pages.</li>
<li>The server repeats the retrieval process at 30-second intervals.</li>
</ol>
<p>The important distinction is that <strong>the 30-second interval applies to the server retrieving match listings, not to the delivery of video streams.</strong></p>
<p>This keeps sports data retrieval separate from actual media delivery.</p>
<p>It also provides a predictable update interval without requiring a separate external data request for every visitor.</p>
<p>There is a tradeoff between freshness and request frequency.</p>
<p>A shorter interval could provide more frequent updates but would increase the number of requests to the data source.</p>
<p>A longer interval would reduce request frequency but might leave the displayed information outdated for longer.</p>
<p>For the current architecture, 30 seconds is the interval I chose.</p>
<p>As the platform develops, there may be opportunities to use different update strategies depending on whether a match is upcoming, live, or completed.</p>
<h2>5. How TVNOON Handles Live Sports Streaming</h2>
<p>This is probably the most interesting part of the architecture.</p>
<p>Many people associate sports streaming websites with video servers, media processing pipelines, and significant bandwidth requirements.</p>
<p>However, TVNOON doesn't operate as a conventional video relay server.</p>
<p><strong>The TVNOON application server does not receive and retransmit video streams to viewers.</strong></p>
<p>Instead, video content is delivered directly from external providers' WebRTC infrastructure to the user's browser.</p>
<p>The application server focuses on website functionality and match information.</p>
<p>The video delivery infrastructure operates separately.</p>
<h3>Understanding the Two Data Paths</h3>
<p>The architecture can be divided into two independent paths.</p>
<p><strong>Match Information</strong></p>
<p>External Sports Data Source → TVNOON Application Server → User's Browser</p>
<p><strong>Video Streaming</strong></p>
<p>External WebRTC Provider → User's Browser</p>
<p>The first path is responsible for sports listings and website information.</p>
<p>The second path is responsible for delivering streaming video directly to the browser.</p>
<p>This separation means that the TVNOON server doesn't need to relay the video traffic for every viewer.</p>
<p>For example, someone searching for 해외스포츠중계 may be looking for information about international football, basketball, or another sporting event.</p>
<p>TVNOON can provide the relevant event information through its application server.</p>
<p>Where an external stream is available, the browser connects to the provider's WebRTC infrastructure for media delivery.</p>
<p>The distinction is particularly important because video traffic has different bandwidth and performance requirements from normal HTML pages or event listings.</p>
<p>Separating these responsibilities helps keep the application architecture focused.</p>
<p>It also means that actual stream availability, playback behavior, and media performance depend on the external provider.</p>
<p>Streaming availability and viewing permissions must be assessed according to the provider's applicable rights and terms.</p>
<h2>6. Why WebRTC Is Part of the Architecture</h2>
<p>WebRTC is a technology used for real-time communication and media delivery through compatible browsers.</p>
<p>In TVNOON, WebRTC is relevant because external providers use it to deliver video content directly to viewers.</p>
<p>The website's Node.js application server doesn't operate the providers' media infrastructure.</p>
<p>Instead, the browser receives the video through the external WebRTC connection.</p>
<p>This creates a useful separation of responsibilities.</p>
<p>The application server can concentrate on generating pages and maintaining sports event information.</p>
<p>Meanwhile, the provider handles media delivery.</p>
<p>However, WebRTC also introduces challenges that need to be considered.</p>
<p>Browser compatibility, connection establishment, network restrictions, and the availability of external media servers can all influence playback.</p>
<p>A streaming interface may work correctly while a video connection fails because of conditions outside the application server.</p>
<p>Understanding this distinction is important when diagnosing problems.</p>
<p>As a developer, I need to distinguish between an issue in the TVNOON website, an issue with the browser, and an issue involving the external media provider.</p>
<p>That makes architecture documentation and clear system boundaries valuable during development.</p>
<h2>7. Designing for International Sports Audiences</h2>
<p>TVNOON is intended to organize information for users interested in different sporting competitions.</p>
<p>International sports coverage presents several challenges that are less obvious than they first appear.</p>
<p>Football competitions take place across multiple regions. Basketball schedules can cross time-zone boundaries. Baseball and volleyball events may have different seasonal patterns.</p>
<p>Users also describe their interests differently depending on language and location.</p>
<p>For example, an English-speaking visitor might search for "live football streaming" or "international sports schedules."</p>
<p>A Korean-speaking visitor might use 축구중계 (football streaming), 해외스포츠중계, or 실시간중계 to look for similar information.</p>
<p>These different expressions are useful when thinking about navigation, content categorization, and search intent.</p>
<p>The challenge is to organize sports information in a way that makes sense to users without creating unnecessary duplication.</p>
<p>A well-designed information architecture should make it easy to understand which sport, event, or competition a page refers to.</p>
<p>This is also relevant to search-engine optimization.</p>
<p>Rather than repeating keywords throughout a page, I prefer to connect search terms to actual content that explains what users can find.</p>
<p>For TVNOON, that means treating 스포츠중계 as a broad topic, 해외스포츠중계 as an international sports category, and 실시간중계 as an interest related to ongoing events.</p>
<p>Similarly, 무료스포츠중계 is a search term associated with users looking for no-cost viewing options. It doesn't mean every event or external stream on a platform is necessarily free or available without restrictions.</p>
<p>Accurate descriptions are more useful than making broad promises about streaming availability.</p>
<h2>8. Challenges I Encountered While Building TVNOON</h2>
<p>Developing a sports information platform requires balancing simplicity with changing technical requirements.</p>
<h3>Challenge One: Managing Frequently Updated Information</h3>
<p>Sports listings need regular updates, but making unnecessary requests can complicate the system.</p>
<p>The 30-second server-side retrieval cycle is my current approach to balancing freshness and request frequency.</p>
<p>It establishes a clear update schedule while keeping the responsibility for retrieving match information on the backend.</p>
<h3>Challenge Two: Avoiding Unnecessary Frontend Complexity</h3>
<p>Modern frontend frameworks offer many useful capabilities.</p>
<p>However, introducing a large framework can also add dependencies, build processes, and development overhead.</p>
<p>For TVNOON, I decided that server-generated HTML was a better fit for the initial architecture.</p>
<p>This gave me a simpler foundation for handling content-driven pages.</p>
<h3>Challenge Three: Separating Streaming from Website Operations</h3>
<p>Video streaming and ordinary website requests have fundamentally different infrastructure needs.</p>
<p>Attempting to process both through the same application server could add significant complexity.</p>
<p>By keeping external WebRTC media delivery separate, I can focus the Node.js application on the features it actually manages.</p>
<h3>Challenge Four: Maintaining a Clear User Experience</h3>
<p>A sports platform can become difficult to navigate as more competitions and content categories are added.</p>
<p>Organizing information clearly is therefore just as important as choosing the right backend technologies.</p>
<p>I continue to consider how users discover matches, navigate between sports, and access relevant information.</p>
<h2>9. What Developing 눈팅티비 Has Taught Me</h2>
<p>One of the most valuable lessons from this project is that software architecture should be driven by requirements rather than trends.</p>
<p>There are many ways to build a modern web platform.</p>
<p>A developer could choose a frontend framework, multiple backend services, an independent database server, and dedicated streaming infrastructure.</p>
<p>Those technologies may be appropriate for certain projects, but they also introduce additional responsibilities.</p>
<p>For TVNOON, I wanted to understand how much could be achieved with a smaller set of tools.</p>
<p>Node.js 22 provides the application runtime.</p>
<p>Express 5 handles HTTP requests.</p>
<p>Built-in SQLite provides data storage.</p>
<p>The server generates HTML.</p>
<p>Match listings are retrieved every 30 seconds.</p>
<p>External WebRTC providers deliver video directly to browsers.</p>
<p>Each component has a defined responsibility.</p>
<p>This structure has helped me think more carefully about where application complexity is actually necessary.</p>
<p>I've also learned that technical simplicity doesn't mean ignoring important concerns.</p>
<p>Error handling, security, database integrity, accessibility, performance, and external service reliability still require attention.</p>
<p>A lightweight architecture should make those responsibilities easier to manage, not provide an excuse to overlook them.</p>
<h2>10. What's Next for TVNOON?</h2>
<p>TVNOON is an ongoing development project, and there are several areas I want to continue improving.</p>
<p>My priorities include refining the organization of sports information, improving the reliability of event listings, and making the website easier to navigate across desktop and mobile devices.</p>
<p>I also want to continue evaluating how the application handles external data requests.</p>
<p>As more information becomes available through the platform, efficient update strategies and database operations will become increasingly important.</p>
<p>Another area of interest is making the streaming integration experience clearer.</p>
<p>Because external WebRTC providers handle video delivery, users should be able to understand when a playback problem may be related to external connectivity or provider availability.</p>
<p>From a content perspective, I want TVNOON to become more useful for people following international competitions, whether they are interested in football, basketball, baseball, or other sports.</p>
<p>That includes users searching for sports schedules, 해외스포츠중계 information, and coverage of ongoing live events.</p>
<p>I also plan to continue documenting the development process.</p>
<p>Topics I'd like to explore in future technical articles include server-side rendering with Express, SQLite database design, handling periodic data updates, and integrating external WebRTC services into a lightweight website.</p>
<h2>Final Thoughts</h2>
<p>TVNOON (눈팅티비) started as an effort to make sports information easier to discover while keeping the underlying application architecture straightforward.</p>
<p>The platform brings together sports event information and browser-based access to externally delivered streaming media.</p>
<p>From a technical perspective, the project demonstrates how Node.js 22, Express 5, built-in SQLite, server-generated HTML, and external WebRTC infrastructure can work together without requiring a large frontend framework.</p>
<p>For users, the focus remains on discovering sporting events and finding useful information related to sports streaming.</p>
<p>For me as a developer, the project is an ongoing opportunity to learn about practical system design, maintainability, and the tradeoffs involved in building a real web application.</p>
<p>I believe good software development is not about adopting every available technology.</p>
<p>It is about understanding the problem, assigning clear responsibilities to each component, and improving the system as real requirements become clearer.</p>
<p>I'll continue sharing my experience building TVNOON and exploring ways to make lightweight web applications more useful and reliable.</p>
<p>If you're developing a project with Node.js, Express, SQLite, or WebRTC, I'd be interested in hearing about the architectural decisions you've made.</p>
<hr />
<p><strong>Project:</strong> TVNOON (눈팅티비)</p>
<p><strong>Official Website:</strong> <a href="https://tvnoon.com/">https://tvnoon.com/</a></p>
<p><strong>Built With:</strong> Node.js 22, Express 5, Built-in SQLite, JavaScript, HTML, Server-Side Rendering, WebRTC</p>
<p><strong>Focus:</strong> Sports Information, International Sports Streaming Information, Live Event Discovery, and Lightweight Web Development</p>
]]></content:encoded></item></channel></rss>