Manually generating client SDKs from an OpenAPI spec is error-prone and blocks releases. Running openapi-generator inside a CI/CD pipeline generates, validates and publishes SDKs automatically on every spec change, with Spectral linting, breaking change detection and contract tests acting as gates.

A data protection breach in an online shop can give affected customers a right to damages under Article 82 of the General Data Protection Regulation, and this now applies to small and medium shops as well, not only to large corporations. We explain in plain language what this means and what to do now.

DI

FACTORY

Deep Dive · Magento 2 Dependency Injection

Injectable vs. Non-Injectable:
The underestimated boundary in Magento

Why Models and DataObjects must never be injected into constructors, how Factories solve this, and exactly what the DI container classifies as "injectable".

12 min read

Magento 2.4.8 · PHP 8.4

Magento DI Concepts

Contents

1. 1. The boundary: what's allowed in constructors?
2. 2. Injectable objects: services and managers
3. 3. Non-injectable objects: models and DataObjects
4. 4. Why models must not be injected
5. 5. Factory as the solution: auto-generated factories
6. 6. Custom factories and factory methods
7. 7. Shared vs. non-shared in di.xml
8. 8. Proxy: lazy loading for expensive injectable objects
9. 9. PHPStan: finding non-injectable violations
10. 10. Conclusion: the golden rule of DI

One of the most common causes of bugs in Magento modules: a Model gets injected directly into a constructor. This is subtly wrong and causes unexpected side effects,

An anti-join finds every row of a table that has no matching row in a second table, a semi-join finds every row that has at least one matching row, without pulling that table's columns into the result. Both patterns solve a common problem, finding customers with no order or products with at least one review, but only one of the common implementations is truly robust with NULL values and performance.

Magento 2 · Upgrade

Magento 2 Upgrade Checklist
from 2.4.x to 2.4.8

An upgrade to Magento 2.4.8 is not a Composer command, it is a technical change process. Anyone who fails to think through compatibility, testing, deployment and fallback up front pays for it later with long analysis phases, broken modules or unnecessary downtime.

21 min read Cheatsheet Magento 2.4.8

Table of Contents

1. 1. What a Magento 2 upgrade to 2.4.8 really means
2. 2. Before the Composer update: technical preparation
3. 3. Checking core, PHP, extensions and third-party packages
4. 4. Running the upgrade process in a controlled way
5. 5. Which tests are mandatory before go live
6. 6. Deploy, cache and production release
7. 7. Typical upgrade pitfalls
8. 8. Quick upgrade vs. controlled upgrade path
9. 9. Magento 2 support
10. 10. Summary and FAQ

1. What a Magento 2 upgrade to 2.4.8 really means

Magento 2 upgrade 2.4.8 often sounds smaller than it actually is in a real project. Even when the version jump on

Passwords in Dockerfiles, API keys as ENV variables, certificates baked into image layers: these are real security holes in thousands of container setups. Docker Secrets, BuildKit mount secrets, and well-designed credentials management eliminate these risks without slowing down the development workflow.

If you wait for the server to respond before the UI moves, you are giving away perceived speed. useOptimistic solves this problem right at the core of React: the UI state jumps forward immediately, gets adopted on success, and rolls back cleanly on failure, without manual state management.

Anyone maintaining a .gitlab-ci.yml in more than one repository knows the problem: build, test and deploy jobs get copied over and over, and slowly drift apart. The include keyword solves exactly this, merging pipeline definitions from other files, other projects, or even external URLs at pipeline compile time. This article walks through all four include variants in detail and shows how they combine into a central CI template library for an entire organization.

Reactive programming is solved differently in every modern frontend framework, with incompatible APIs and abstractions hidden behind framework boundaries. The TC39 Signals proposal defines a universal foundation for the first time: Signal, computed, and effect as native JavaScript primitives that frameworks can build on.

Planning server storage around rigid partitions runs into limits the moment you need to grow. LVM decouples logical volumes from the physical disk layout and lets you resize, snapshot, and add new disks while the application keeps running, with no restart required.