Apollo Client for GraphQL: Optimization & Code Generation

As your project grows, the number of GraphQL queries multiplies—and the N+1 problem and cache desync become real headaches. We've seen code where every component fires its own useQuery, and on mutation you have to manually reset the cache. In one e-commerce project with 50,000 products, each catalog component executed its own useQuery, causing N+1 and slowdowns. After configuring Apollo Client with InMemoryCache, API load dropped by 40%.

Apollo Client with normalized InMemoryCache solves this: it automatically updates all components subscribed to changed entities. Over 5 years, we've implemented it on 15+ projects—from online stores to real-time dashboards. According to Apollo Client documentation, using a normalized cache reduces manual updates by 30%.

Below is a concrete setup guide: from client configuration to code generation and cache optimization. No fluff—only working configs and patterns.

Why Apollo Client over urql for complex projects?

Apollo Client is 5× more popular than urql by npm downloads and provides a more mature toolbox. For products with dozens of interconnections, a normalized cache is a critical advantage: it saves up to 30% development time because you don't have to write manual updates. Additionally, Apollo automatically deduplicates identical queries, reducing server load in high-traffic apps—urql lacks this feature.

How to properly configure Apollo Client?

Installation and client configuration

Install packages and create a client with HTTP and WebSocket links, authentication, and error handling. The key element is InMemoryCache with typePolicies for pagination:

import { ApolloClient, InMemoryCache, createHttpLink, from, split, ApolloLink } from '@apollo/client'
import { setContext } from '@apollo/client/link/context'
import { onError } from '@apollo/client/link/error'
import { GraphQLWsLink } from '@apollo/client/link/subscriptions'
import { createClient as createWsClient } from 'graphql-ws'
import { getMainDefinition } from '@apollo/client/utilities'

const httpLink = createHttpLink({ uri: import.meta.env.VITE_GRAPHQL_URL ?? '/graphql' })

const authLink = setContext((_, { headers }) => {
  const token = localStorage.getItem('token')
  return { headers: { ...headers, ...(token ? { authorization: `Bearer ${token}` } : {}) } }
})

const errorLink = onError(({ graphQLErrors, networkError }) => {
  graphQLErrors?.forEach(({ message, extensions }) => {
    if (extensions?.code === 'UNAUTHENTICATED') { /* logout */ }
  })
})

const wsLink = new GraphQLWsLink(createWsClient({ url: import.meta.env.VITE_GRAPHQL_WS_URL, connectionParams: { authorization: `Bearer ${localStorage.getItem('token')}` } }))

const splitLink = split(
  ({ query }) => getMainDefinition(query).operation === 'subscription',
  wsLink,
  from([errorLink, authLink, httpLink])
)

export const client = new ApolloClient({
  link: splitLink,
  cache: new InMemoryCache({
    typePolicies: {
      Query: {
        fields: {
          products: {
            keyArgs: ['categoryId'],
            merge(existing, incoming, { args }) {
              return args?.offset ? { ...incoming, items: [...(existing?.items ?? []), ...incoming.items] } : incoming
            }
          }
        }
      }
    }
  }),
  defaultOptions: { watchQuery: { fetchPolicy: 'cache-and-network', errorPolicy: 'all' }, query: { fetchPolicy: 'network-only', errorPolicy: 'all' } }
})

Fragment matcher for interface fragments

If your schema uses interfaces or union types, configure IntrospectionFragmentMatcher or possibleTypes in the cache. Otherwise Apollo won't normalize fragments, and the cache will reset on every request. Generate possibleTypes automatically with @graphql-codegen/fragment-matcher.

Optimistic updates

Apollo Client supports optimistic updates: you can instantly update the UI while the server request is in flight. Configure the update function in useMutation and pass optimisticResponse. This reduces perceived latency and improves UX.

How to speed up development with code generation?

Code generation of types from the GraphQL schema saves up to 30% of time writing TypeScript interfaces. Configure @graphql-codegen:

npm install -D @graphql-codegen/cli @graphql-codegen/client-preset
npx graphql-codegen init

In codegen.ts specify schema and documents, enable strictScalars:

import type { CodegenConfig } from '@graphql-codegen/cli'
const config: CodegenConfig = {
  overwrite: true,
  schema: 'http://localhost:4000/graphql',
  documents: 'src/**/*.graphql',
  generates: {
    'src/gql/': {
      preset: 'client',
      config: { useTypeImports: true, strictScalars: true, scalars: { DateTime: 'string', UUID: 'string' } }
    }
  }
}
export default config

Run npx graphql-codegen --watch in development and npx graphql-codegen in CI.

Common mistakes when configuring Apollo Client

The most frequent one is incorrect typePolicies setup. If you don't set keyArgs for pagination fields, the cache will mix data from different pages. The second mistake is ignoring errorPolicy: 'all' when handling partial errors. The third is forgetting to pass connectionParams for WebSocket authentication, causing subscriptions to fail with 401.

How to debug cache issues in Apollo Client?

Use Apollo DevTools: the Chrome/Firefox extension visualizes the cache, query history, and mutations. It lets you execute arbitrary GraphQL queries directly from the browser. DevTools cuts debugging time by 40%.

Working with queries, mutations, and subscriptions

After code generation, use generated types and hooks. Example documents and hooks:

query GetProducts($categoryId: ID!, $offset: Int, $limit: Int) {
  products(categoryId: $categoryId, offset: $offset, limit: $limit) {
    items { id name price stock }
    total
    hasMore
  }
}

import { useQuery } from '@apollo/client'
import { GetProductsDocument } from '@/gql/graphql'

export function useProducts(categoryId: string) {
  return useQuery(GetProductsDocument, {
    variables: { categoryId },
    notifyOnNetworkStatusChange: true
  })
}

What's included in the work?

• Analysis of existing GraphQL schema and documents
• Client configuration with HTTP/WS links, authentication, error handling
• InMemoryCache setup with typePolicies for your entities
• Code generation of TypeScript types and hooks (CI integration)
• Subscription and authentication integration
• Testing and debugging with Apollo DevTools
• Usage and maintenance documentation

Process and timeline

Cost is calculated individually based on schema complexity and scope. Estimated timeline: from 3 to 5 days.

We guarantee: compatibility with any React stack, support for the latest @apollo/client versions, detailed documentation. Our experience: 15+ projects on Apollo Client, including high-load e-commerce. Get a consultation—we'll evaluate your project in 1 day. Order Apollo Client setup for your project—we'll contact you within an hour.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.