GraphQL

AI generated

GraphQL Schema Design: Fields, Types, Interfaces and Unions Done Right

Maxim Mironjuk - May 02, 2026

A poorly designed schema is hard to extend, forces breaking changes, and makes resolvers complex. The right nullability decisions, custom scalars, and correct use of interfaces and unions determine how long a GraphQL API stays viable.

Magento GraphQl REST-API

AI generated

OpenAPI vs. GraphQL: Where Both Models Complement Each Other

Maxim Mironjuk - April 25, 2026

The question isn't "OpenAPI or GraphQL?", it's "What is each model good for, and when does it make sense to run both in the same system?" Anyone who understands both models and their respective strengths makes better API architecture decisions.

Magento GraphQl REST-API Security/OWASP

AI generated

Persisted Queries: Security and Performance in GraphQL

Maxim Mironjuk - April 07, 2026

Persisted Queries solve two problems at once: they reduce the amount of data transferred and close a security gap that is often overlooked in public GraphQL APIs. Anyone who accepts arbitrary queries hands attackers a free pass. Anyone who only allows known queries gains control, without sacrificing flexibility entirely.

Magento GraphQl Security/OWASP Testing/E2E

AI generated

Extending Magento GraphQL Customer Data Securely

Maxim Mironjuk - April 01, 2026

Integrating custom fields into the customer types, securing resolvers with token validation, exposing extension attributes correctly, and protecting sensitive data at the field level, all in one hands-on practical article.

Magento GraphQl REST-API

AI generated

Cart and Checkout in Magento GraphQL: Architecture, Limits, Debugging

Maxim Mironjuk - March 10, 2026

The checkout flow in Magento GraphQL is complex: seven mutations from cart creation to order placement, sessionless state management via the cart ID, and a series of typical error sources that are hard to pinpoint without good debugging. This article shows how the flow works, where its limits lie, and how to systematically find errors.

Magento GraphQl

AI generated

Input Types vs. Custom Scalars: Which One When?

Maxim Mironjuk - March 04, 2026

In GraphQL schema design, the question of input types versus custom scalars leads to regular discussions. Both solve similar problems in different ways. The difference does not lie in capability, but in semantic intent: does the type describe a structure or a value range?

Magento GraphQl

AI generated

Combining Resolver Caching and Edge Caching

Maxim Mironjuk - February 28, 2026

GraphQL and caching are often seen as a difficult pair, because every request hits the same endpoint and CDNs do not cache POST requests by default. With the right combination of application-level resolver caching and edge caching through persisted queries, the problem can be solved systematically.

Symfony

AI generated

API Platform 4: REST und GraphQL ohne Boilerplate in Symfony | mironsoft.de

Maxim Mironjuk - February 11, 2026

Wer eine REST- oder GraphQL-API in Symfony von Hand aufbaut, schreibt Controller, Serializer-Konfigurationen, Pagination und Fehlerbehandlung selbst. API Platform 4 übernimmt das alles deklarativ — eine PHP-Klasse mit dem richtigen Attribut reicht, um eine vollständige API-Ressource mit Filterung, Pagination und OpenAPI-Dokumentation zu erhalten.

Magento GraphQl

AI generated

Federation, Stitching and BFF: Which Architecture When?

Maxim Mironjuk - January 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.

Magento GraphQl PHPUnit Testing/E2E

AI generated

Building Mutations in Magento: Input, Service Contract, Response

Maxim Mironjuk - January 11, 2026

A GraphQL mutation is more than a resolver with side effects. Anyone who doesn't model input types in the schema, writes business logic directly into the resolver, or fails to return errors as a structured response ends up with an API that is hard to test, document, and extend.