RelationalDBDesignRelationalDBDesign 


Web Applications   «Prev  Next»
Lesson 11

Web-based Oracle Applications Conclusion

Module summary

The Web paradigm is very similar to the three-tiered client-server architecture.
  1. WebServer performance and tuning can be addressed only from the time an URL request is received by the Web Listener, until the completed request has been serviced and returned to the client.
  2. Most Web applications use some sort of alternative concurrency locking scheme because of the unreliability of the Internet.
  3. Alternative locking schemes involve re-reading rows and comparing the current row contents to the prior row contents.
  4. Web applications should have a separate server to handle and route the incoming Web requests.
  5. Oracle provides many methods for Web connectivity, including the Web Request Broker, and CGI.
  6. Oracle Web application should be designed only to retrieve the amount of information that the end-user desires on one page. Declaring and holding cursors can be unreliable.
This module covered the basic concepts behind Web-based Oracle applications, and showed various techniques for maintaining Oracle performance. Now that you have completed this module, you should be able to:
  1. Describe how Web applications connect to an Oracle database
  2. Describe the function of the Oracle Web Architecture
  3. Use the Oracle Web Request Broker
  4. Describe how Oracle manages incoming Web requests
  5. Design Web applications for high performance
  6. Show locking problems with Web applications
  7. Describe and implement alternative concurrency mechanisms for Web applications

Glossary Terms

Here are some terms that may be new to you.
  1. Hypertext Markup Language (HTML)
  2. concurrency management

Execution Plan Techniques - Quiz

To complete this module, click the Quiz link below to check your knowledge of advanced execution plan techniques.
Execution Plan Techniques - Quiz