The Database: a Processing Engine, or a Persistence Layer?

We have many years of extensive hands-on experience of building, and tuning, applications that use Oracle Database. We have seen two mutually incompatible architecture paradigms. The thick database paradigm, preferred in the 1990s, starts with the design of the relational model. This leads naturally to the encapsulation of all insert, update, delete, and select statements within PL/SQL subprograms that expose the database interface. The NoPlsql paradigm, which seems now to be the preferred choice, starts with an object oriented domain model in the middle tier, and leads naturally to treating the database as a bag of tables, letting the primitive SQL statements that manipulate these express the API.

In Part 1, we describe the awful problems brought by the NoPlsql paradigm. We discuss its performance implications and debunk the myth that “moving business logic out of the data tier and into the middle tier” improves performance and scalability. We examine the time and effort implications and show that projects that adopt the NoPlsql paradigm use most of their resources on developing “plumbing” code rather than code that implements actual business functionality. These problems are just the tip of the iceberg and we expose several other serious drawbacks.

The widespread adoption of the NoPlsql paradigm has made the world a worse place, and so in Part 2, we explain the thick database paradigm, rehearse the reasons for its superiority, and describe how to adopt it. The paradigm implies more than just allowing database calls to invoke only PL/SQL subprograms. We formalize a layered code classification scheme which leads to optimal understandability and maintainability of both your PL/SQL and your SQL code – which properties bring the maximum probability of correct behavior. This approach establishes the database tier as a reliable central service provider in your application landscape. We will convince you that following the thick database paradigm, and implementing your business functions within the database, guarantees the avoidance of the awful problems brought by the NoPlsql paradigm.  

Biografie spreker: Toon has been part of the Oracle eco-system since 1987. He is currently a member of Oracle's Real World Performance team. The RWP-team troubleshoots application performance issues in and around the DBMS. The way applications currently use (or rather, abuse) the DBMS, is often at the root of these performance issues. Prior to joining the RWP team, Toon has been mainly involved in database application development. His special interests are: architecting applications for performance and scalability, database design, and business rules / constraints modelling. He is a long-time champion of the Thick Database paradigm.

18.30 ontvangst met broodjes etc. (dieetwensen svp voor 1 november doorgeven aan
19.00 start programma
21.00 afsluiting met borrel

Datum: Maandag 7 november 2016
Spreker: Toon Koppelaars
Taal presentatie: Nederlands 
Locatie: Oracle, Hertogswetering 163 - 167, Utrecht
Parkeren: De Wall P3. Bij vertrek kunt u zelf uw parkeert stempelen bij de balie

Aanmelden bij voorkeur voor 1 november.
Leden OGh kunnen zich aanmelden op de gebruikelijke wijze via de website
Niet-leden die interesse hebben kunnen zich aanmelden voor een aspirant lidmaatschap(gratis) voor 1 maand. ze kunnen een verzoek aan richten en ontvangen dan de inloggegevens. zodat ze zich kunnen aanmelden voor dit event.Na afloop van die maand vervalt het aspirant lidmaatshap automatisch maar het kan dan desgewenst omgezet worden in een lidmaatschap van de OGh.
Er zijn 3 soorten lidmaatschap.Voor nadere informatie over het OGh lidmaatschap ga naar of mail naar
tel. 030 6997065
U kunt zich niet meer inschrijven voor dit evenement.
Het evenement heeft al plaatsgevonden.