GraphQl: Guides and Practical Know-how | Page 13 | mironsoft Blog
GraphQl
-
Jan 28, 2025
API Platform automatically generates queries and mutations from every resource, but as soon as an action combines several resources or real time updates are needed, you need a custom GraphQL resolver. This article shows how query resolvers, mutation resolvers with dedicated input classes, and Mercure based subscriptions work together in API Platform.
-
Jan 21, 2025
GraphQL authorization does not end at the query check. Sensitive fields such as email addresses, order histories, and admin-specific data must be secured at the field level, inside the resolver context, not just in the schema. This article shows how that works in practice.
-
Jan 20, 2025
GraphQL sends queries as a POST request to a single endpoint, which makes standard HTTP caching harder than in REST. Anyone who takes GraphQL performance seriously needs to understand every caching layer: Persisted Queries for HTTP caching, resolver-level response cache, and CDN edge caching for non-personalized content.
-
Jan 16, 2025
Headless commerce with Magento GraphQL promises flexibility. In practice, Apollo Client configuration, type-safe code generation, SSR/SSG caching and fragment design decide whether the frontend stays fast and maintainable or turns into a complexity trap.
-
Jan 11, 2025
In many GraphQL projects, the schema is the only contract between frontend and backend teams, yet nobody takes responsibility for versioning, sharing or reviewing it. Introspection, SDL and schema registries are the three building blocks that let teams turn the schema into a genuine single source of truth.
-
Jan 5, 2025
A schema with three different styles for the same thing costs every team time, patience, and trust in the API. Clear GraphQL naming conventions for types, fields, mutations and enums make a schema self-explanatory and can be anchored in a team for good with a style guide and linting.
-
Jan 5, 2025
Magento GraphQL can be extended in a targeted way, but opening up the schema without preparation builds performance problems into your project through N+1 database queries. The right approach goes through extension attributes, cleanly isolated resolvers, and a clear separation between schema definition and data access.
-
Jan 4, 2025
Every plugin increases memory usage, extends startup time, and can slow the IDE down. The question is not which plugins exist, but which ones genuinely add value to your own workflow, and which ones can be disabled without any loss.
-
Jan 4, 2025
Loading data directly from the database inside GraphQL resolvers quickly produces hundreds of individual queries per request once fields get nested. The DataLoader Pattern collects these loading requests within a single tick, executes them as one batch, and caches the results per request, without forcing resolvers to give up their simple, isolated structure.