The document discusses the benefits of using PL/SQL for building applications that interface with an Oracle database. It notes that PL/SQL allows developers to hide implementation details and expose just the interface, making applications more correct, maintainable, secure and high-performing. The document recommends that skeptics who argue against using PL/SQL attend a session that will show why PL/SQL is important and provide unassailable arguments in its defense. It also provides links to resources like a whitepaper and video interview that further explain the reasons for using PL/SQL.

1. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Lighting in hotel rooms

2. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Having a shower

3. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Spell checking

4. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Opening a door

6. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Why use PL/SQL?
Bryn Llewellyn
Distinguished Product Manager
Database Division
Oracle HQ
twitter: @BrynLite
May 2016

7. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for
information purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described for Oracle’s products remains at the sole discretion of Oracle.

8. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
AMIS 25 – June 2016
Large software systems must be built from modules. A module hides its
implementation behind an interface that exposes its functionality. This is computer
science’s most famous principle. For applications that use an Oracle Database, the
database is the persistence module. The tables and the SQL statements that
manipulate them are the implementation details. The interface is expressed with
PL/SQL. Developers and users of applications built this way are happy with their
correctness, maintainability, security, and performance. But when developers follow
the NoPlsql paradigm, their applications have problems in each of these areas and
users suffer. This session provides PL/SQL devotees with unassailable arguments to
defend their beliefs against attacks from skeptics. Skeptics who attend will see the
light.

9. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.
Whitepaper download
• My presentation slides are no use without me presenting them
• I have written a whitepaper that gives a careful and detailed account
of what my presentation addresses
– Go to the PL/SQL page on OTN: oracle.com/plsql
– Click the “Learn More” tab
Notice the link to the Oracle Database PL/SQL and EBR blog
– Notice the blog that announces the “Why use PL/SQL?” whitepaper
– Notice my Twitter handle @BrynLite. I’ll tweet news on updates to the paper
– Watch this six-minute interview at DOAG (the German Oracle User Group):
www.doag.org/en/home/aktuelle-news/article/plsql-so-gehts.html

10. Copyright © 2015, Oracle and/or its affiliates. All rights reserved.