Benjamin Canac

I’ve been wondering why we don't see more people adopting the "shared nothing" model that PHP-FPM uses. Years ago, the argument against it was clear: process scheduling and context switching were expensive. Other languages went the route of shared state and long-lived processes because it was more efficient for things like async I/O. That made sense at the time. But today, context switching is much cheaper than it used to be. Meanwhile, the benefits of the shared nothing model have only become more obvious. The amount of cognitive overhead it removes for a developer is huge. You don't have to worry about memory leaks between requests or state bleeding from one user to another. Every request starts fresh. I think that simplicity is a huge part of why PHP still dominates such a massive portion of the web. I get why people didn't build this way 30 years ago, but I don't really understand why nobody else has tried to offer a similar model in the past 15ish years. There was a great article by Nicolas Grekas recently about how they handled over 1,000 concurrent screens in real-time at SymfonyCon. He showed how stable the PHP-FPM model is, but also acknowledged where it hits a wall (like massive amounts of concurrent connections) and how he handled that specific part differently. It’s a great look at using the right tool for the job without throwing away the simplicity of the shared nothing foundation. The link is here if you haven't seen it: https://lnkd.in/dmqva_SH Does anyone actually know why this architecture isn't more common in other ecosystems? Is there a technical reason I'm missing, or is it just a matter of "that's not how we do things here" or some ego-driven need for what we perceive as "clean architecture" over pragmatism? I'm curious to hear what you think.

20

9 Yorum

Claude Code in Drupal !?!?!?! Well we've got it kind of working: https://lnkd.in/e7e8pxw5 Here's a quick peak at Drupal using the Claude Agent SDK which calls a claude code cli binary runtime on your server. We have streaming, a terminal like experience. However, I think this isn't actually far off something we could use in Drupal. Our existing Drupal AI agents could just plug into this! We'd get the full power of Claude Code's innovation but all the infrastructure and modules already in Drupal CMS and built by the community! Hoping to work with Shibin Das and David Galeano Barrado from Factorial to bring flowdrop's much nicer UI to controlling Claude Code Agents. Thanks to Roland Obermair for helping me with this! Dries Buytaert Scott Falconer John Faber #Drupal #DrupalAI #ClaudeCode #ClaudeAgentSDK #DoitwithDrupalsoon!

204

16 Yorum

What's new at Private Packagist, August update: dependency usage tracking across your packages, automatic GitLab token rotation, and Conductor improvements with custom labels and smarter PR handling. Read the full details on our blog 👇  #php #composer #composerphp #phpc https://lnkd.in/efu-xDrB

10

1 Yorum

Headless Drupal is not for everyone. Here’s when it changes the game. I see headless Drupal work best in three main cases: → When you need high performance, like fast load times or lots of content → When your site needs a complex front-end, with more control over the user experience → When you want to share content across many platforms from one backend You get some strong advantages: • Pick any front-end technology you want, like React • Improve speed and scalability with a decoupled system • Create one source for content that goes everywhere But there are trade-offs: • Setup and maintenance are more complex than with standard Drupal • You need more technical skills on your team • Costs can go up, since you need both front-end and back-end developers When does a traditional Drupal setup make more sense? → If you need a simple website with basic content management → If your team is not ready for a lot of technical setup → If you only need to support one website or platform I work with businesses of all sizes — from corporate platforms to custom LMS and e-commerce solutions and see both options in action. Headless Drupal can be a powerful solution if your needs match the use cases above. For many projects, traditional Drupal remains the easier, more cost-effective choice. If you want to learn more about which setup fits your business, feel free to reach out. Let’s connect if you’re planning your next web project. #Drupal #WebDevelopment #ContentManagement #APIDevelopment #TechLeadership

4

your react app probably doesn't need a complex router with dozen of options, but just a hook to subscribe to history changes and a function to match on pathname patterns → https://lnkd.in/eawK_QCA

12

4 Yorum

🚀 Symfony AI 0.6 will ship with a Claude Code bridge for the CLI This means you’ll be able to use Claude Code directly from your Symfony workflows in the terminal. AI + CLI + Symfony = 🔥 What would you build with this? Code analysis? Refactoring? Test generation? AI-powered dev workflows? 👀 Curious to hear your wildest use cases! 👇

97

12 Yorum

Why Drupal’s boring features are its best ones The shiny stuff — AI integrations, low-code builders, decoupled frontends — gets all the hype. But Drupal’s real staying power comes from the features that quietly do the heavy lifting every day. Views — the query builder that never quits. It turns any entity into sortable, filterable, paginated data without touching SQL. Half the “custom dashboards” you’ve seen in Drupal are just clever Views setups. Webform — not technically core, but so tightly integrated it feels like it. It handles surveys, registrations, and multi-step workflows that would take weeks to code anywhere else. JSON:API — built in, standards-based, and always consistent. It turns Drupal into a reliable data source for anything that needs structured content — no extra wiring required. Blocks — simple on the surface, but still one of the most flexible layout systems around. Context-aware placement, custom fields, reusable components — they quietly hold entire design systems together. Add configuration management, permissions, and caching, and you’ve got a platform that’s stable, predictable, and wildly adaptable — all without chasing trends. The point: Drupal’s “boring” features aren’t outdated. They’re what make the whole thing work. #Drupal #WebDevelopment #DigitalExperience #OpenSource #EnterpriseTech #Drupal10 #JSONAPI #Views #Webform #CMS

71

13 Yorum

🚀 Symfony + API Platform = Clean, Scalable, Enterprise APIs If you're building modern APIs with PHP, this combination is seriously powerful. When I started using Symfony with API Platform, I realized something: You don’t just build APIs faster — you build them *properly*. 🔥 Why Symfony + API Platform? 1️⃣ API-First by Default With API Platform, your entities can instantly become fully functional REST or GraphQL APIs. ```php #[ApiResource] class Product {   #[ORM\Id]   #[ORM\GeneratedValue]   #[ORM\Column]   private ?int $id = null;   #[ORM\Column]   private string $name; } ``` That’s it. You automatically get: * GET collection * GET item * POST * PUT / PATCH * DELETE * Swagger / OpenAPI docs * Validation support Minimal code. Maximum power. 2️⃣ Built on Symfony’s Strong Foundation You get: ✔ Dependency Injection ✔ Security (Voters, Roles, Firewalls) ✔ Event System ✔ Messenger (async processing) ✔ Doctrine ORM It’s not just an API generator — it’s enterprise-ready architecture. 3️⃣ Automatic Documentation Swagger UI is generated automatically. Clients and frontend teams can test endpoints instantly. No extra setup. No third-party tool required. 4️⃣ Advanced Features Out of the Box * Pagination * Filtering * Sorting * Serialization groups * Custom operations * DTO support * GraphQL You focus on business logic — not boilerplate. 5️⃣ Perfect for Modern Stack Symfony + API Platform works beautifully with: * React * Vue * Next.js * Mobile apps * Microservices * SaaS platforms It’s truly backend-for-frontend ready. 💡 Biggest Realization Laravel is amazing for rapid development. But Symfony + API Platform feels like: “Let’s build this API the right way from day one.” Clean structure. Strong security. Scalable design. --- If you’re building serious APIs in 2026, this stack deserves your attention. Are you using API Platform already? 👇 #Symfony #APIPlatform #PHP #BackendDevelopment #RESTAPI #GraphQL #WebDevelopment

5

🤖 Symfony AI 🤖 "With the release of Symfony 7.4 and the maturity of the Symfony AI Initiative, we finally have a first-class citizen for building AI-native applications. While symfony/ai-platform handles the chat models, the real game-changer for business applications is symfony/ai-store. This component is the backbone of Retrieval-Augmented Generation (RAG) in PHP. It abstracts the complexity of vector databases - whether you’re using Redis, PostgreSQL (pgvector), or Elasticsearch - into a clean, recognizable Symfony interface." https://lnkd.in/emPx6atq

14

Want to build a custom CMS without having to wrestle with backend setup? We have the solution for you! In this blog post, Thibault Barrat walks you through how to build a flexible and dynamic CMS with minimal code using Supabase and React-admin. Why this combo works so well: ⚡ Supabase: A powerful, all-in-one backend that gives you a Postgres database, authentication, and storage right out of the box. ⚛️ React-admin: The go-to open-source framework for building admin panels. It's fully customizable and saves you hours of repetitive setup, so you can focus on your unique business logic. 🤝 Together, they integrate seamlessly and offer you an easy way to manage content, whether for a personal project, a client, or an internal tool. 🔗 Check out the full tutorial here: https://lnkd.in/edJ5zpNi #CMS  #WebDevelopment #OpenSource #JavaScript #FullStack #React #ReactAdmin #Supabase #Postgres

7

Tailwind Weekly 199 🔥 🌙 Tailwind CSS adds full dark mode for Tailwind Plus ✨ "Tailwind CSS by Example" course is coming soon 📚 Neurodiversity design, simpler Observer APIs, Partial Keyframes 🎁 Resource: tweakcn theme editor Dive in 👇 https://lnkd.in/eXgzFVJz

3

🚀 JetRails AutoPilot Update – September 2025 JetRails Developers crushed AutoPilot once again 👏👏 with cloning, new PHP/LEMP templates, Valkey support and smoother autoscaling all landed. Highlights include: Clone your deployment (finally) New PHP/LEMP app hosting PSR-0 fix for faster performance Valkey (Redis fork) support Finance-only user roles Wildcard domains by default Patches? Oh, there are plenty. Bug fixes? Too many to list. 👀 Changelog → https://lnkd.in/g_kFWpjv 👀 #JetRails #AutoPilot #EcommerceHosting #Magento #Shopware #CloudInfrastructure #DevOps

3

We were discussing this within the #Drupal community a couple of days ago, after I shared this link internally. This is truly important and feels like a natural, #Symfony-like move. Since Drupal already relies heavily on Symfony components, everyone agrees that it makes sense to consider utilizing these building blocks more systematically in the future. If we do this for routing or dependency injection, then why not for AI agentic contracts or MCP fundamentals? But then, an even more interesting idea emerged from people who are part of multiple communities: What if we aimed to deliver something like what Vercel does in the Javascript arena? A single PHP SDK for all the big players? Why not build the foundational building blocks for AI integration? A group of components that could be used and, most importantly, built collaboratively by #WordPress, #Drupal, and #Laravel people? And #Symfony is obviously a leading candidate to power this project. I’m not sure about WP, but Laravel also quite extensively relies on Symfony low-level components. And truly, http routing, filesystem management, DI, or the way you expose MCP endpoints are not the things that differentiate you anymore. What you build on top of them does. So having these foundational units stable and standardized would benefit every player. Obviously this idea comes with a lot of challenges, but it's definitely a worth exploring by all communities. https://lnkd.in/dSi9Qjn8

16

2 Yorum