GraphQl: Guides and Practical Know-how | Page 3 | mironsoft Blog
GraphQl
-
Feb 8, 2026
With Schema-First, the SDL file comes first and becomes the contract between frontend and backend. With Code-First, a library generates the schema from classes and decorators. Both paths produce a working GraphQL API, yet they differ fundamentally in tooling, team structure, and long-term maintainability.
-
Feb 4, 2026
A single Node process can hold thousands of WebSocket connections for GraphQL Subscriptions, but once multiple server instances run behind a load balancer, a publish event loses contact with clients attached to other processes. Redis Pub/Sub, Kafka and clean connection management solve this fan-out problem and make GraphQL Subscriptions horizontally scalable.
-
Jan 31, 2026
Apollo Federation v2, schema stitching and the Backend for Frontend pattern all solve the same underlying problem: coordinating distributed GraphQL data access. Which pattern fits when depends on team size, ownership boundaries and runtime requirements.
-
Jan 28, 2026
GraphQL caching in Varnish is not an automatic side effect, it is a deliberate architectural decision: persisted queries turn variable POST bodies into cacheable GET requests, X-Magento-Tags enable precise invalidation, and IdentityInterface decides which resolvers are even allowed to contribute to the cache. This article walks through the full path from request to invalidation.
-
-
Jan 25, 2026
A shared GraphQL API for multiple tenants saves infrastructure, but carries a real risk: one forgotten tenant filter in a resolver, and tenant A sees tenant B's data. Building tenant isolation systematically instead of ad hoc avoids exactly that scenario.
-
Jan 24, 2026
A search feature that returns products, categories, and pages in one list outgrows any single object type. Union types and interfaces give GraphQL the tools to model such heterogeneous results without compromising type safety or introspection, with clear rules for which tool fits when.
-
Jan 21, 2026
A naive GraphQL resolver that triggers its own database query for every list item quickly produces hundreds of individual queries on nested queries. GraphQL batching following the DataLoader pattern collects these requests and resolves them in a single, efficient call, with a noticeable impact on response times and database load.
-
Jan 19, 2026
Magento ships its GraphQL endpoint without type information for the client, which leaves storefront code trusting field names and nullability on faith. graphql-code-generator automatically generates TypeScript types and typed query documents from the real schema, so broken field access and forgotten null checks show up at compile time instead of in a real customer's checkout.
-
Jan 19, 2026
The PHPStorm HTTP Client fully replaces Postman for many developers: .http files versioned in the repo, environments for dev/staging/prod, variables for tokens and IDs, response handlers for automatic assertions. For Magento REST and GraphQL there are specific patterns that make testing considerably easier.