drivolution
play

DRIVOLUTION: RETHINKING THE DATABASE DRIVER LIFECYCLE Emmanuel - PowerPoint PPT Presentation

Sep 12, 2022 •262 likes •486 views

DRIVOLUTION: RETHINKING THE DATABASE DRIVER LIFECYCLE Emmanuel Cecchet (UMass Amherst) Joint work with George Candea ( ) THIS RESEARCH IS BASED ON TRUE EVENTS U UN APPROPRIATE FOR BOTH ACADEMIC AND INDUSTRIAL AUDIENCES

  1. DRIVOLUTION: RETHINKING THE DATABASE DRIVER LIFECYCLE Emmanuel Cecchet (UMass Amherst) Joint work with George Candea ( )

  2. THIS RESEARCH IS BASED ON TRUE EVENTS U UN APPROPRIATE FOR BOTH ACADEMIC AND INDUSTRIAL AUDIENCES

  3. DATABASE DRIVERS PHP Application MySQL drivers: 63 platforms, 14+ languages libmysl Connect or/ nat ive lib ODBC Java Application Connect or/ J .Net Application MySQL JDBC Driver JVM Connect or/ Net mysql network protocol Perl script Python DBD::mysql MyS QLdb DB-API

  4. DATABASE DRIVER LIFECYCLE Get an appropriate driver package from vendor 1) Install the driver on the client application machine 2) Configure the client application to use the driver 3) Start the application and load the database driver 4) Connect to database and check protocol compatibility 5) Authenticate 6) Execute requests 7) Driver update: Stop the application 8) Uninstall old driver 9) 10) Repeat all steps 1 through 7

  5. STATE OF THE ART IN DATABASE DRIVERS  Drivers are not sexy…  Driver distribution separate from database engine  Driver installation manual process on client machine  Driver upgrades are disruptive (client application reconfiguration + restart)  No protection against malicious drivers

  6. A REAL LIFE EXAMPLE  200 application servers accessing a cluster of 4 DBs  Driver upgrade more complex than database upgrade  Online upgrades? Interne t DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver DB Driver

  7. DRIVOLUTION Think different  Concepts  Implementation  Use cases

  8. DRIVOLUTION CONCEPTS  2 Components: Application 2 Application 3 Bootloader and Server Application 1 Drivolution JDBC Drivolution Bootloader Bootloader Drivolution  Drivers are stored in Bootloader Driver 1 the database Drivolution protocol Database protocol information schema Drivolution Server  Generic bootstrap receives driver a la API API platform binary binary version format code DHCP from 4.0 jar JDBC JRE 1.6 Driver 1 Drivolution server ODBC 3.0 linux_i386 zip Driver 2 ODBC 3.0 ADO.Net zip Driver 3  Lease associated to driver with various Database renewal policies

  9. DRIVOLUTION CONCEPTS Application Drivolution Drivolution Bootloader Server send(db, user, API, platform) DRIVOLUTION_REQUEST find_available_driver(API, platform) send(lease, driver_bin_format) DRIVOLUTION_OFFER set(lease_expire_time, send(driver_code) expire_policy) TFTP or download(driver_code) secure transfer update lease table load(driver) set (user, client@, driver id, lease) connect() … DRIVOLUTION_REQUEST Lease expires Upgrade driver update lease table DRIVOLUTION_OFFER Install new driver send(driver_code) Switch according to policy

  10. DRIVOLUTION Think different  Concepts  Implementation  Use cases

  11. DRIVOLUTION BOOTLOADER  Database driver agnostic but API[/Platform] specific  Implements the Drivolution protocol  Can load multiple drivers and switch from 1 version to the other  Does not need to be upgraded

  12. DRIVOLUTION SERVER  Server logic uses regular SQL  re-uses all existing database mechanisms  logic can be implemented as a stored procedure  In-core implementation  Drivolution server embedded in the database  can enforce connection closing on server side upon lease expiration Application 1 1  External server Drivolution Server Bootloader legacy  Server runs outside the DB 3 Driver 2 driver 2  uses legacy driver to access DB 4 driver table  Standalone server Driver 1  database independent service Driver 2  generic driver distribution server Legacy Database

  13. DRIVOLUTION IN A JAVA WORLD  Bootloader can be integrated in JVM runtime  Very small footprint (8 KB)  Drivers loaded in separate classloaders  No runtime overhead after 1 st connect (original driver code)

  14. DRIVOLUTION Think different  Concepts  Implementation  Use cases

  15. DRIVOLUTION USE CASES: HETEROGENEOUS DATABASE ADMIN

  16. DRIVOLUTION USE CASES: DYNAMIC RECONFIGURATION OF CLIENTS  Master/slave failover for planned maintenance  0-downtime operation  Failback = downgrade

  17. DRIVOLUTION USE CASES: DATABASE CLUSTERS  Drivolution server as a standalone driver distribution service  Useful for both legacy and homogeneous systems  Can be replicated for HA

  18. DRIVOLUTION: OTHER USE CASES  Assembling drivers on-demand  extensions on-demand (NLS, GIS, Kerberos…)  driver code signing to identify malicious drivers  dynamic generation of preconfigured drivers  License server  license keys in separate files  static or dynamic distribution  Integration of Bootloaders in runtime libraries

  19. WHAT IS THE MESSAGE TO TAKE BACK HOME?

  20. CONCLUSION  Drivers are not sexy… but they deserve our attention https://sourceforge.net/projects/drivolution/  More open issues in Sigmod’08 paper MIDDLEWARE-BASED DATABASE REPLICATION: THE GAPS BETWEEN THEORY AND PRACTICE

  21. QUESTIONS? Contact: cecchet@cs.umass.edu

Recommend

More recommend