A REVIEW ON DEDICATED AND MULTITHREADED SERVER ARCHITECTURES

The way servers handle multiple client requests has evolved dramatically over the past three decades. This paper takes a detailed look at two major approaches: dedicated servers built for specific tasks and multithreaded servers designed to handle many operations at once. We studied six important research papers published between 1992 and 2024 to understand how these systems work and when to use them. Our findings show some interesting patterns. The Parallella board, for instance, uses just 5 watts of power while handling web traffic, that's about as much as a small LED bulb. Meanwhile, database systems using Enhanced Client-Server designs can process over 1,000 jobs per minute compared to just 40 jobs for traditional setups. We found that thread pool architectures work well for most general applications, while specialized systems shine when you need energy efficiency or have very specific requirements. The paper includes several comparison tables showing performance numbers, energy usage, and scalability limits. These help readers understand which architecture makes sense for different situations- whether you're building a mobile app, running a database, or setting up IoT devices. The trade-offs are clear: simple designs are easier to build but don't scale well, while complex distributed systems can handle thousands of users but require more expertise to implement and maintain.