The API is slow under real load
A nested resolver firing once per parent row, usually because DataLoader is missing or the query is not batched at the database.
Batched with DataLoader, measured
Working with GraphQL?
Most GraphQL APIs that reach us look fine in the playground and fall over under real traffic, usually because a resolver is firing hundreds of times per request. We find the resolvers that are actually doing the damage and fix them, without redesigning the whole schema.
What it is
GraphQL is a query language and runtime for APIs, developed internally at Facebook from 2012 and released publicly in 2015. It is now stewarded by the GraphQL Foundation under a neutral open specification.
Clients send a query written against a typed schema, and server resolvers produce the data for each field. Transports are usually HTTP POST for normal queries and WebSockets through graphql-ws for subscriptions. Implementations exist for every major language, including Apollo Server, Yoga, Hot Chocolate, Graphene, Juniper and gqlgen.
Common architectures are a single schema per service, Apollo Federation for joining several services into one graph, and tools like Hasura or Postgraphile that generate a schema straight from a database.
The honest version
No technology is all upside. This is where GraphQL earns its place and where it tends to cause trouble.
Sound familiar?
The GraphQL problems that bring people to us, and what you have once each one is fixed.
A nested resolver firing once per parent row, usually because DataLoader is missing or the query is not batched at the database.
Batched with DataLoader, measured
Authorisation lives on each resolver, and one or two fields were never checked, so users see records that belong to someone else.
Object-level checks on every field
One subgraph is slow or down and the gateway waits on it, so every client request stalls even for fields it does not need.
Timeouts, retries and clean degradation
No depth or complexity limits, so a nested query from one client ties up CPU and database connections for everyone else.
Depth and cost limits in place
Introspection left on in production, sometimes together with GraphiQL, hands attackers a complete map of the API.
Introspection off, playground gated
The plugin and cache APIs changed between major versions, and custom auth or logging plugins stopped loading after the bump.
Ported to the new plugin API
Several teams publish their own subgraphs and nobody owns the combined view, so field names and types no longer line up.
One curated, reviewed schema
What we do
Call us for one slow query, or hand us the whole graph.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. We read the schema, walk through the resolvers, work out which fields are actually used by clients, and document what is there before changing anything. In most cases the API can be stabilised in place without a rewrite.
A field resolver that looks up related records fires once for every parent row, so a query that returns fifty authors runs the books lookup fifty times. The fix is usually DataLoader for batching inside the request, or pushing the join down into a single database query.
Authentication belongs in middleware that runs before any resolver and puts the user on the context. Authorisation belongs on each resolver or type, often with directives or a shared helper, so object-level permissions are checked for every field that returns sensitive data.
If several clients need different shapes of the same data, or a mobile app wants fewer round trips, GraphQL earns its keep. For simple server-to-server APIs with stable payloads, REST is often less work to run.
Yes. We design the subgraph boundaries, set up the gateway with timeouts and retries, add contract tests so one team cannot break another, and put schema review in place so the combined graph does not drift.
Estimates are free. Describe what the API is doing and you get a price before any work begins.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: