3+ Features Developers Use That Might Never Make It to PostgreSQL
summary
Application developers want to run language-native functions directly on database nodes to avoid packaging, copying and redeploy cycles: demo compiles a Java JAR, installs it into Postgres via PL/Java and shows the pain of rebuilds, contrasts that with Ignite’s one-click compute tasks executed on DB nodes and Snowflake/PLV8 in-DB JS wrappers, and migrates a Google Cloud SQL app to a Yugabyte cluster with no app changes to prove distributed reads/writes and geo resilience work. PL/Java vs PLV8 vs Ignite
AI-written summary · about
chapters (5)
- 0:00Introduction and setup
- 1:57Compute tasks for developers
- 25:20Distributed storage and query
- 43:46High performance computing
- 49:00Q&A session
related talks
20mLeveraging PLV8 in Javascript heavy Web Applications
29m10 Features your Developers are missing when 'Stuck' with proprietary database!
52mPostgreSQL and Java: Best Practices
41mApplication Development Challenges with Postgres
44mPostgreSQL for Developers
49mSELECT 'amazing features' FROM "postgresql"
33mExtending your database server's abilities
40mDB for next project? Why, Postgres, of course