|
2605 | 2605 | "excerpt": "Software security should always be in the back of your mind as a developer. It may seem fine at first to deliver a feature sooner, only to find later on that you left a backdoor into your crisp new update.", |
2606 | 2606 | "tl_dr": "Software security should always be top of mind for a developer, since ignoring it can lead to major costs, data loss, GDPR fines, or the loss of client trust. The article surveys many facets of software security and walks through the practical measures Dotkernel Headless Platform takes for each: input validation, content negotiation, CORS, RBAC, demo credentials, error reporting, OpenAPI docs, PHP and JavaScript dependencies, OAuth2, session/cookie settings, and CI checks.", |
2607 | 2607 | "tags": [] |
| 2608 | + }, |
| 2609 | + { |
| 2610 | + "post_title": "Dependency Injection vs. Factory Design Pattern", |
| 2611 | + "post_date": "2026-10-12 12:00:00", |
| 2612 | + "post_status": "published", |
| 2613 | + "author": { |
| 2614 | + "display_name": "Florin Bidirean", |
| 2615 | + "github": "bidi47" |
| 2616 | + }, |
| 2617 | + "isObsolete": false, |
| 2618 | + "opengraph_img": "/opengraph/article/twitter-card-dependency-injection-vs-factories-design-pattern.png", |
| 2619 | + "excerpt": "Dotkernel's dot-dependency-injection package lets you wire a service with an #[Inject] attribute or a hand-written factory. This article compares both approaches with real dotkernel/api code and explains when each one fits.", |
| 2620 | + "tl_dr": "Attributes remove one factory file per service and keep dependencies next to the constructor they feed, while hand-written factories keep static type checking and full control over construction. Use #[Inject] for plain constructor wiring, keep factories for computed, conditional, decorated or third-party classes, and mix both freely in the same PSR-11 application.", |
| 2621 | + "tags": [] |
2608 | 2622 | } |
2609 | 2623 | ] |
2610 | 2624 | }, |
|
3127 | 3141 | "excerpt": "Choosing a lightweight PHP framework for a microservice is less about which option is smallest and more about which complexity you want to own. This article compares Dotkernel API, Slim 4, and Lumen, looking at various features and tradeoffs.", |
3128 | 3142 | "tl_dr": "Dotkernel API, Slim 4, and Lumen take very different approaches to building lightweight PHP microservices. Explore how they compare in terms of simplicity, authentication, authorization, database support, operational tooling, dependency management, and long-term maintainability—and understand why the right choice depends on whether you need a genuinely minimal service or an authenticated API designed to evolve over time.", |
3129 | 3143 | "tags": [] |
3130 | | - }, |
3131 | | - { |
3132 | | - "post_title": "Attributes vs. Factories in Dependency Injection", |
3133 | | - "post_date": "2026-10-12 12:00:00", |
3134 | | - "post_status": "published", |
3135 | | - "author": { |
3136 | | - "display_name": "Florin Bidirean", |
3137 | | - "github": "bidi47" |
3138 | | - }, |
3139 | | - "isObsolete": false, |
3140 | | - "opengraph_img": "/opengraph/article/twitter-card-dependency-injection-vs-factories-design-pattern.png", |
3141 | | - "excerpt": "Dotkernel's dot-dependency-injection package lets you wire a service with an #[Inject] attribute or a hand-written factory. This article compares both approaches with real dotkernel/api code and explains when each one fits.", |
3142 | | - "tl_dr": "Attributes remove one factory file per service and keep dependencies next to the constructor they feed, while hand-written factories keep static type checking and full control over construction. Use #[Inject] for plain constructor wiring, keep factories for computed, conditional, decorated or third-party classes, and mix both freely in the same PSR-11 application.", |
3143 | | - "tags": [] |
3144 | 3144 | } |
3145 | 3145 | ] |
3146 | 3146 | } |
|
0 commit comments