Hello! Would we classify Prisma as schema-driven development 🙂 ?

I suppose you could. I guess it’s always a question of context. But indeed, the schema in Prisma is very explicit in comparison to other DB access libraries.

If you get the term from the GraphQL world, schema vs. code first, then it might be slightly different of course but still follow the same ideas.

Thanks guys! I’m asking because I’m writing a blog post about schema-driven development. Roughly the technologies I want to touch on are: • GraphQL ( SDL-first and code-first ) : mostly for client-server communications • gRPC: mostly for server-server communications • Prisma: server - database Touching on benefits like type-safety, clear intentions between teams, etc. Would something like that make sense or am I grouping things together where I shouldn’t?

Makes sense to me

I guess it’s always a question of context.

Major plus one +1 on what Daniel said here. The term "schema-first" development is not really well-defined IMO, so if you're planning to write an article about it, I'd definitely include your own understanding/definition of the term and then start analyzing how the different technologies fit into it. FWIW, we've defined the term "schema-first" (or "schema-driven" as follows) in this article:

The term schema-first is quite ambiguous and in general conveys a very positive idea: Making schema design a priority in the development process.