User-driven Apps: Securely Build for Defined DBMS Users
summary
A profile-driven system maps DB-level views and permissions to real user roles and auto-provisions service endpoints, cutting repetitive handoffs and weekly rework. Implementation uses role-based access control, profile-driven provisioning and a single canonical data store with segregated collections; projects link to a single entry point for each user cohort. Measured outcomes: repository activity up ~25% year-over-year and core web blocking time commonly under 2.5s, which validates faster developer onboarding and fewer security mistakes in production.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 3:46Core components of user-driven apps
- 7:09Security by design principles
- 11:51Role-based access control
- 15:42Dynamic design for flexibility
- 20:20Simplifying data management
- 24:01Demo of project tracking system
- 26:25Choosing the right model
- 29:08Developer community growth
- 31:18Web performance metrics
- 32:44Open discussion and Q&A
related talks
40mIn the Pursuit of the Best Developer Experience
27mUser Adoption as Proxy for Business Benefit Realization
30mProduction › Prototype: How a Small Team Replaced a Core Platform in 90 Days
21mDriving Platform Adoption: Embedded SRE
47mPanel: Insights from Internal Developer Portal Rollouts in Large Enterprises
46mWhen Software Becomes Everyone's Job
38mEnabling Developer Experience Journey in U.S. Bank
27mLessons Learned Implementing Meaningful Access Controls...