Should Hasura prioritize expanding GraphQL API features or improving the PostgreSQL integration for its core engine?

Introduction

The trade-off between expanding GraphQL API features and improving PostgreSQL integration for Hasura's core engine is a critical decision that will shape the product's future direction. This scenario involves balancing the needs of developers using Hasura's GraphQL capabilities against enhancing the core functionality with PostgreSQL. I'll analyze this trade-off by examining the product context, potential impacts, and proposing a data-driven approach to make an informed decision.

Step 1

Clarifying Questions (3 minutes)

• Context: I'm thinking Hasura's current market position might influence this decision. Could you share our current market share and main competitors in the GraphQL API space?

Why it matters: Helps understand competitive pressures and market opportunities Expected answer: Growing market share, competing with Apollo and Prisma Impact on approach: Would influence whether to focus on differentiation or core strengthening

• Business Context: Based on our revenue model, I assume enterprise customers are a key segment. How does our enterprise vs. open-source user split look, and which group typically requests more features?

Why it matters: Aligns decision with revenue drivers and user needs Expected answer: 60% enterprise, 40% open-source; enterprise users request more PostgreSQL features Impact on approach: Would prioritize improvements that cater to paying customers

• User Impact: I'm guessing different user segments have varying needs. Can you break down our user base by experience level (beginner vs. advanced) and their typical feature requests?

Why it matters: Ensures we're addressing the needs of our most valuable users Expected answer: 70% advanced users, often requesting more PostgreSQL integration features Impact on approach: Would lean towards improving core PostgreSQL integration

• Technical: Considering our current architecture, how much effort would expanding GraphQL features require compared to improving PostgreSQL integration?

Why it matters: Assesses feasibility and resource allocation Expected answer: PostgreSQL improvements more complex but offer long-term benefits Impact on approach: Would influence timeline and resource allocation decisions

• Timeline: Given our product roadmap, how urgent is this decision, and are there any upcoming releases or partnerships that might be affected?

Why it matters: Helps prioritize the decision within overall product strategy Expected answer: Decision needed within next quarter, potential partnership with major cloud provider Impact on approach: Would accelerate decision-making process and consider partnership implications