{"id":8527,"date":"2018-07-18T19:52:54","date_gmt":"2018-07-18T17:52:54","guid":{"rendered":"https:\/\/www.salvis.com\/blog\/?p=8527"},"modified":"2023-11-08T02:36:10","modified_gmt":"2023-11-08T01:36:10","slug":"is-your-application-smartdb","status":"publish","type":"post","link":"https:\/\/www.salvis.com\/blog\/2018\/07\/18\/is-your-application-smartdb\/","title":{"rendered":"Is Your Application SmartDB?"},"content":{"rendered":"\n

I recently had a few discussions regarding the Smart Database Paradigm (SmartDB) with long-standing customers, new customers, partners, competitors and colleagues. Some people think that using APEX and PL\/SQL in their database application is SmartDB. But it is not that simple. Bryn Llewelyn defined the term “Smart Database Paradigm” (SmartDB) in his talk Guarding your data behind a hard shell PL\/SQL API<\/a>. Based on his definition a SmartDB application must have the following five properties:<\/p>\n\n\n\n

    \n
  1. The connect user does not own database objects<\/a><\/li>\n\n\n\n
  2. The connect user can execute PL\/SQL API units only<\/a><\/li>\n\n\n\n
  3. PL\/SQL API units handle transactions<\/a><\/li>\n\n\n\n
  4. SQL statements are written by human hand<\/a><\/li>\n\n\n\n
  5. SQL statements exploit the full power of set-based SQL<\/a><\/li>\n<\/ol>\n\n\n\n

    These five properties are not a set of recommendations. They are the bare minimum. Either your application has these properties or not. It’s binary. There is (almost) no room for interpretation. Here’s an excerpt of a longer Twitter thread, making my and especially Bryn Llewelyn’s view a bit clearer.<\/p>\n\n\n