PostgresQL as an Application Modernization
summary
Claim: migrate legacy systems onto Postgres and you get SQL/ODBC/JDBC/REST access day one while keeping original behavior. Implementation: build a driver that intercepts old platform calls, add a DB API, move schemas into Postgres and optionally pair with Axelor for web/mobile UI. Outcome: a 400-program COBOL app runs unchanged yet five slow jobs drop from ~30 minutes to under a minute; estimated developer effort falls up to 80% and compliance, extensibility and hiring become practical.
AI-written summary · about
chapters (13)
- 0:00Intro
- 4:02Migrate (Lift and Shift) and Modernization What We Provide
- 10:09Four Main Solution Components To Bridge the Gap
- 16:07How PostgreSQL Can Help Applications Evolve
- 16:21Stage 01: No Change
- 17:10Why an RDBMS: Program Centric vs Data Centric
- 18:28Database Migration Runtime
- 20:01Application and Database Migration
- 26:3204 Database Modernization Features Gained
- 29:58Consolidated Model
- 31:56Application and Database Modernizace Modernization in Place
- 32:44Modernized Application
- 36:29For More Information
related talks
46mPostgreSQL, REST API's and Rapid Application Development for Legacy Data
30mAn Assessment-to-Adoption Path from Oracle, SQL Server, Sybase, DB2 onto
06mMigration Consideration Oracle to PostgreSQL
29mTales from the Field - Oracle to PostgreSQL migrations
41mApplication Development Challenges with Postgres
37mDatabase Modernization at Cloud Scale: Minimizing Risk and Disruption
48mMigrating to PostgreSQL: Strategies, Sovereignty, and Success
44mPostgres for Java Developers