Data Portals: Using PostgreSQL server-side cursors for secure and ...
summary
Uses PostgreSQL named server-side cursors (psycopg2 NamedCursor) to hand a preloaded query resultset between apps, plus short-lived Postgres user accounts and row-level-security to enforce access, and a Python contextmanager cleanup to revoke access and close the connection. Targets bi-directional transfers measured in gigabytes to hundreds of gigabytes, avoids JSON serialization overhead, improves lower-percentile latency and throughput, and works when clients are few and trusted; not suitable for many concurrent untrusted clients or very frequent small requests.
AI-written summary · about
chapters (5)
- 0:00Start
- 6:07Option 1: Add some webservers
- 8:18Option 2: Common staging area
- 11:43Summary: Problem Constraints
- 14:59What is a portal?
related talks
52mPostgreSQL and Java: Best Practices
49mPostgreSQL - the database-sister of Python
46mUse PostgreSQL to Step Up Your Game
22mDjango with PostgreSQL superpowers
40mPostgreSQL Security for Application Developers
50mPostgreSQL gotchas for app developers
51mHow Postgres is Different (read BETTER than) your database
23mDjango with PostgreSQL superpowers