A middleware system between web and database servers
0 likes529 views
The document discusses a middleware system designed to enhance performance between web and database servers by managing connections and optimizing access. It addresses issues of overload in backend servers and proposes a service broker that assigns requests efficiently while minimizing hardware costs. The solution aims to improve overall website performance through better connection management and query optimization.
A middleware system between web and database servers
- 1. A Middleware System between WEB and Database Servers Mohammad H. Abu-Arqoub, Ihab S. Serhed, Waheeb A. abu-Dawwas, and Rashid M. Al-Azzeh HanYang Univ Lee Hyun Dong
- 2. 1. INTRODUNCTION - Current web servers do not support overload control, service differentiation, and caching of contents generated by backend servers. - Backend system becomes overloaded because dynamic application uses one connection for each dynamic application, there is no connections’ management.
- 3. 2. THE PROBLEM’S DEFINITION (I) - The major problems can be addressed are managing accesses to the database backend server. - The Application Programming Interfaces currently used in web applications, reside in the application process’ space and share no information with other processes. - The drawbacks of this paradigm ● Backend servers become overloaded due to the entire request handling process. ● Access is isolated and not globally optimized. ● The overhead induced by contexts switching
- 4. 2. THE PROBLEM’S DEFINITION (II) - Solution, for each request to the database, the web server will : ● Receives the request from the client. ● Forwards this request to our Service Broker system, and then the Server Broker will assign it to one of the running threads that follow a parent class to let all running threads be shared for a specific application.
- 5. 3. TYPICAL WEB SERVER PARADIGM (I) - Web server environment typically consists of two parts : front-end and backend - In front-end, there is a set of dynamic applications that usually run at known ports. These dynamic application are used as connectors between clients and backend servers.
- 6. 3. TYPICAL WEB SERVER PARADIGM (II) - Once the request arrives, it will be redirected to the appropriate dynamic application that assigns a thread to handle it.
- 7. 4. WEB SERVER PARADIGM USING SERVICE BROKER SYSTEM - Service Broker uses a limited number of open connections to the database server, to be used without repeatedly establishing connections, and without shutting down.
- 8. 5. THE PROPOSED SERVICE BROKER SYSTEM (I) - The simplest way to improve a website’s performance is by scaling up the hardware. - Service Broker system improves the performance without extra costs for the hardware by providing some recommendations that were shown to be helpful in improving the performance. - Service Broker system is used as a middleware or as an intermediate process between a front-end web server and a backend server instead of API that have to access a database server.
- 9. 5. THE PROPOSED SERVICE BROKER SYSTEM (II) A. Database Connection Management B. Query Optimization - Searching process did not consume a lot of time to find whether the same query has been executed twice by two requests simultaneously. Service Broker Architecture
- 10. 6. CONCLUSION - A possible way to improve performance of a web server is by using a database Service Broker for decreasing the overload on the database backend server was developed.