Jake Moshenko, CEO of AuthZed, discusses the importance of permissioning databases and the challenges of implementing permissions at scale. He explains how AuthZed solves this problem by providing a common API for flexible and fine-grained authorization. The target market for AuthZed includes companies of all sizes that need to add complex permission workflows to their applications. Jake demonstrates how AuthZed can be integrated with backend systems, web applications, and mobile apps. He also explains the benefits of using AuthZed, such as increased security and improved product velocity. The conversation concludes with a discussion on the AuthZed schema language and how permissions and roles are defined in the system. Jake Moshenko introduces the concept of permissions and relations in the context of access control. He explains how permissions can be granted to users for specific actions on resources, and how relationships between users and objects are defined. Jake also discusses the flexibility of defining roles and the granularity of permissions. He demonstrates how permissions can be visualized and edited in a user interface, and highlights the benefits of using a startup solution for access control. The conversation concludes with a discussion on the importance of leveraging existing tools and trusting innovative startups.
Takeaways
Chapters
00:00 Introduction and Background
01:04 The Problem of Permissions at Scale
05:25 Implementing Authorization for Different Client Types
06:46 Integration with Backend and Web Applications
10:24 Implementing Permissioning for Mobile Apps
14:25 Benefits of Using AuthZed for Permissioning
22:00 Granting Access to Resources with AuthZed API
25:11 Defining Permissions and Roles in AuthZed
30:42 Introduction to Permissions and Relations
31:11 Understanding Permissions and Roles
32:20 Decoupling Relationships and Actions
33:36 Granularity of Permissions
34:14 Grouping Privileges into Roles
36:01 Design Time and Runtime Actions
36:46 Visualizing and Editing Permissions
39:33 Trusting a Startup
53:36 Building vs. Buying Solutions
58:36 The Value of Innovation and Trust
Building a Mobile App - Part I (Starting to build a native mobile app, and wondering which way to go?)
Building a Mobile App - Part II (React Native, Flutter, and some others)
Aggregations in Mongo - Much faster and the best (and maybe only?) alternative in many cases
Make your Git commits frequent so you run into fewer merge conflicts
Heroku Cloud Application Platform - why it will help your TTM (Time to Market)
Building a Brand New Application? Looking for a way to reduce your ramp up time?
Development Efficiency - Are you bouncing your servers too often?
Code Quality - How can you assess the quality of a codebase before reviewing a single line of code?
Backwards Compatibility Issues - a few ways to ensure that you do not run into them
Native Mobile App - Design Patterns & Separation of concerns (Part 1)
Native Mobile App - Design Patterns & Separation of concerns (Part 2)
Databases & Denormalization - Faster queries for faster retrieval
Reusable UI components (React and beyond) - both presentational & functional
Caching - What to Cache, and When to Cache (Part 3)
Caching - Are you optimizing before identifying the problem? (Part 2)
When looking to make performance improvements, it is natural to look for that ”single” big problem. But, that’s hardly ever the case.
Keep your code DRY. As in, super DRY! Code duplication is a maintenance nightmare.
Libraries vs Frameworks (based on my rather loose definition of it!) - What’s your preference?
Should you implement that next requirement now, later or never?
[Paid Course] Snowpal Education: Writing scripts to understand REST APIs
Join Podbean Ads Marketplace and connect with engaged listeners.
Advertise Today
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast