Skip to Main Content

#SmartDB Office Hours

Should the database be used as a persistence layer only, or as a full-fledged processing engine that runs business logic too? We believe that “processing engine” is the right answer. Moreover, we believe that the database should be exposed to client-side programs only through a PL/SQL API. We call this approach the SmartDB paradigm, and we use this name as our Twitter hashtag. We argue that SmartDB is the proper way to build correct and secure applications on Oracle Database. We especially like that the approach brings, as a happy side-effect, best performance and maintainability. Use these sessions to put any and all questions that you might have about SmartDB to Bryn Llewellyn and Toon Koppelaars.

DS

Replays

Resources

  • #SELECTION#
    #ICON_HTML#

    Why Use PL/SQL? An Argument for the SmartDB Paradigm

    "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 paper provides PL/SQL devotees with unassailable arguments to defend their beliefs against attacks from skeptics. Skeptics who attend will see the light." Bryn Llewellyn, PL/SQL Product Manager
    #MISC#
    #ACTIONS#
  • #SELECTION#
    #ICON_HTML#

    The SmartDB Resource Center

    A collection of resources to help database developers build applications following the SmartDB paradigm. To sum up: SQL statements (select, insert, update, delete, merge, commit, and rollback) are issued only from database PL/SQL.
    #MISC#
    #ACTIONS#
  • #SELECTION#
    #ICON_HTML#

    Why SmartDB?

    A presentation by Toon Koppelaars on why the SmartDB approach is the best fit for most common transactional database applications. It offers a path to the most secure, highest performing and easiest-to-maintain APIs to your data.
    #MISC#
    #ACTIONS#
  • #SELECTION#
    #ICON_HTML#

    JavaScript's MVVM enables revival of #SmartDB

    Short deck used in 2nd #SmartDB Office Hours session, on why the current JavaScript architecture enables the #SmartDB approach to revive.
    #MISC#
    #ACTIONS#