Customer story
How one tech lead built Elsevier's peer-review MVP in ten months with Prisma
Elsevier, a global leader in scientific publishing, set out to modernize a slow, manual peer-review process. Led by a single tech lead, the team built a meaningful MVP in ten months on Prisma, and it now processes real scientific publications.
Prisma Client, Prisma Migrate, and Nexus let one engineer move fast, experiment with the data model, and keep frontend and database types in sync, so the product could change quickly based on user feedback.
About Elsevier
Elsevier is a global leader in information and analytics for scientific publishing, helping researchers and healthcare professionals advance science and improve health outcomes. This project set out to modernize its peer-review workflow for journal publications.
Industry
Scientific publishing / information analytics
Scale
Global
Stack
TypeScript, GraphQL, Nexus, AWS Lambda
Using
Prisma Client · Prisma Migrate · Nexus
The challenge
Elsevier's peer-review process for scientific publications was manual, outdated, and slow, a logically complex workflow that needed modernizing to stay competitive in healthcare research.
Rebuilding it came with real constraints:
“The flexibility of moving fast and changing the product based on user feedback fast was crucial.”
A logically complex workflow. Multi-user document editing needs a nested data structure, not flat records.
Speed of iteration mattered. The product had to change quickly as user feedback came in.
A very small team. Much of the build rested on a single tech lead, so hand-writing boilerplate wasn't an option.
Why Elsevier chose Prisma
The team chose Prisma to move fast without writing and maintaining the usual boilerplate. Paired with Nexus for code-first GraphQL, Prisma removed the manual work of definitions, resolvers, schemas, and models, while keeping everything type-safe in TypeScript.
GraphQL with the nested data it needed
Nexus gave the multi-user document editing a nested structure, code-first.
Less boilerplate to hand-write
Prisma eliminated manual definitions, resolvers, schemas, and models.
Frontend and database types in sync
TypeScript throughout kept application types aligned with the database.
How they use Prisma
The MVP is built around a Prisma and Nexus package that holds the schema, migrations, and generated types. AWS Lambda functions use Prisma Client to update resources directly, and the business logic backed by Prisma serves both the GraphQL API and the frontend. Everything is written in TypeScript, so database and frontend types stay synchronized.
Handling schema changes is a big part of why it worked for a small team. As Serghei Ghidora put it: “When it comes to the data model experimentation, handling migrations, you run the migrations and Prisma will do everything by itself.”
On type safety, they said: “Your frontend application types are always in sync with what's available on the database level. That's a big, big deal.”
generator client {
provider =
}
model User {
id String @id @default(cuid())
email String @unique
DateTime
posts Post[]
}
model Post {
String @id
author User @relation
}
Schema valid
The results
One tech lead turned a complex, manual process into a working product that runs on real publications today.
MVP in 10 months
A meaningful MVP delivered in ten months.
Built by 1 tech lead
A large, complex product driven largely by a single engineer.
Live on real publications
Processing real scientific publications, holding up with few critical bugs as it moves toward full production.
Prisma is one of the bricks of that foundation.
Serghei Ghidora, Tech Lead at Elsevier
Build on the same stack as Elsevier
Prisma helped one tech lead take a complex workflow from MVP to real publications. Start building on it today.
- Free to start, no credit card required
- One TypeScript stack your agent can operate end to end
- Trusted by 500K+ developers

