MichalLytek / MichalLytek/type-graphql

Recommendation: Benchmarks

Open
#71 5 comments 0 reactions 0 assignees View on GitHub
Chore :hammer: Community :family_man_girl: Discussion :speech_balloon: Help Wanted :sos:
Dominant language
TypeScript
Stars
8.1k
Forks
672
PR merge metrics
No merged PRs in 30d

Description

It'd be a good idea to have benchmarks against vanilla graphql-yoga plain resolvers. Perhaps keeping it simple and not including the extras of course. Just @Arg / @Context / @Root / @*Type decorators against vanilla graphql, etc.

Might make it easier to help optimize where needed or show the world that class mapping is actually beneficial (because I tried going back to vanilla graphql + manage my own schema and no object mapping and realized how much I enjoy using classes for defining schema)

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Start by locating any existing benchmark tooling and the resolver/decorator examples in the repository, then define a minimal comparison with graphql-yoga plain resolvers and TypeGraphQL decorators. Done means reproducible results covering the requested decorators and a clear comparison of schema and resolver performance.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
api, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.