Volodymyr Matsola

Magento 2 just turned 10 — but is it still thriving, or simply surviving? Once hailed as one of the most powerful open-source e-commerce platforms, Magento has seen a steady decline in popularity over the past few years. As someone who's been part of the ecosystem, I’ve seen first-hand how we got here — and why Magento, despite its strengths, lost momentum. Here’s my perspective on the key reasons behind its decline: ### The Migration Trap The transition from Magento 1 to Magento 2 was anything but smooth. For many businesses, it felt less like an upgrade and more like a full rebuild. The early adopters faced instability, bugs, and a lack of experienced M2 developers — and that left a lasting impression. ### Complexity = Cost Magento's architecture is robust and elegant, but that comes with complexity. Quality implementations demand more time, deeper expertise, and higher budgets — making it harder to justify for small to mid-sized merchants. ### Frontend Challenges Magento’s frontend offers strong architecture from a flexibility and extensibility standpoint. However, it also relies on deprecated JavaScript libraries and outdated frontend patterns. In some areas, like the Checkout, the implementation feels overly complex and difficult to customize efficiently. ### The Adobe Shift Since Adobe’s acquisition, Magento (now Adobe Commerce) has doubled down on the enterprise and B2B segment. That strategic pivot has alienated many smaller merchants and agencies who once drove the community forward. ### Rise of Faster, Cheaper Alternatives Platforms like Shopify and others have changed the game — offering faster, cheaper go-to-market options that appeal to the majority of e-commerce businesses. And yet, I still believe Magento/Adobe Commerce remains the best platform for building truly custom, high-performance online stores. When flexibility, scalability, and deep integrations are critical — it’s hard to beat. I've reflected more deeply on Magento’s evolution in my latest blog post: https://lnkd.in/e-_v8XAq Would love to hear your thoughts: Where do you see Magento heading in the next 5 years? #Magento #AdobeCommerce #ecommerce #Shopify #DigitalCommerce #WebDevelopment

19

7 коментарів

Real impact doesn’t make noise. It makes progress. At DDD, we don’t overstate. We build quietly, deliver consistently, and let our work speak: “Before DDD, I had potential. After DDD, I had proof.” This isn’t about being the loudest in the room but about being the most trusted partner in it. Here’s how we’ve helped organizations and talent grow, with 5 proven practices that elevate digital capacity: 1️⃣Real-world client exposure 2️⃣Future-ready tech training 3️⃣Mentorship from global professionals 4️⃣Global standards, locally applied 5️⃣Career-aligned pathways No fluff. No shortcuts. Just frameworks that work and keep working. For leaders building future-proof teams, let’s talk. #ChangeHowTheWorldWorks #DigitalCapacity #CorporateTraining #FutureOfWork #DDDWay

8

The Magento story most people don't know: Back in 2007, when Varien was building what would become Magento, ...they opened an office in Kyiv, Ukraine. These Ukrainian developers weren't just "helping out". They were writing the core code that millions of stores would eventually run on. I've been deep in Magento for over a decade, have built quite a few stores, and currently teach Magento developers at Macademy. But many of us building on this platform today don't realize that we're building and standing on foundations laid by Ukrainian engineers. After years of working remotely and scattered across the globe, the Ukrainian Magento community is coming back together for Meet Magento UA on September 4 in Kyiv! It's the community that built the platform returning to where it all started. If you're in the region or know someone who is, it would be great to check it out. These are the folks who shaped the eCommerce platform that powers a huge chunk of the internet's stores. It's also a great way to respect the roots! 🇺🇦 Get more info about the MMUA25 at https://lnkd.in/g9m5i-8W

372

30 коментарів

🚀 Midweek Spark for Magento & AI Enthusiasts! 🤩 💡 The Future of SEO Isn’t Search; It’s Understanding!! For years, we’ve optimized for Google... But now… AI systems like ChatGPT, Claude, and Gemini are learning to read and understand our websites. Yet most eCommerce stores remain invisible in this new AI discovery era. That’s why this innovation truly stands out 👇 Introducing "LLM.txt for Magento 2 / Mage-OS" - A groundbreaking, AI-powered module that helps your store speak the language of AI. Developed by our brilliant David Lambauer and Michiel Gerritsen, this open-source module uses OpenAI to automatically generate optimized llms.txt files. Helping AI systems understand your store’s content with precision and context. Here’s what makes it powerful: 🤖 AI-Powered Generation - Uses OpenAI to intelligently curate your store content 📝 Smart Content Selection - Automatically analyzes categories, products, and pages ⚡ One-Click Generation - Click a button, review, and publish ✏️ Fully Editable - Edit AI-generated content or write your own 🏪 Multi-Store Support - Different content per store view 🚀 Performance Optimized - Full Page Cache integration 📊 Token Counter - Ensures content stays under recommended limits 🎯 Standards Compliant - Follows llmstxt.org specification In short, it’s robots.txt, reimagined for AI. 🎯 A simple file that bridges eCommerce and the AI-first web. 🔗 Explore it here: https://lnkd.in/dCtwBV5z Huge respect to David Lambauer & Michiel Gerritsen for this brilliant contribution to the Magento & Mage-OS ecosystem 🙌 AI is redefining how content gets discovered. #Magento #MageOS #AIinCommerce #EcommerceInnovation #FutureOfSEO #OpenSource

27

1 коментар

🧠 Understanding Symfony Service Container in Simple Words When I started learning Symfony, the term “Service Container” felt complicated. But once I understood it, everything about Symfony’s architecture started making sense. Let me explain it simply 👇 🔹 What is the Service Container? Think of it as a smart factory. Instead of manually creating objects like this: $mailer = new Mailer(); $logger = new Logger(); $userService = new UserService($mailer, $logger); You just write: public function __construct(UserService $userService) And Symfony automatically: ✅ Creates the object ✅ Injects its dependencies ✅ Manages its lifecycle That’s called Dependency Injection. 🔹 Why Is It Powerful? Because it gives you: ✔ Cleaner code ✔ Loose coupling ✔ Easier testing ✔ Better scalability ✔ Enterprise-level structure Your classes don’t create dependencies. They receive them. That small shift changes everything. 🔹 What Is Autowiring? Autowiring means Symfony reads your type hints and automatically figures out: • What service you need • How to build it • What to inject No messy configuration. No manual wiring. Just smart architecture. 🔹 Real-World Example Imagine building: • User Registration • Email Notifications • Logging • Database operations Your UserService may depend on: MailerInterface LoggerInterface EntityManagerInterface Symfony injects all of them automatically. Your controller stays clean. Your business logic stays focused. Your application becomes maintainable. 💡 Why This Matters In small projects, you may not notice the difference. But in large applications with: 100+ services APIs Background workers Event listeners The Service Container becomes the backbone of your system. This is one of the reasons Symfony is trusted in enterprise applications. Understanding the Service Container changed the way I think about backend development. It’s not just about making code work. It’s about building software that lasts. If you're learning Symfony, don’t skip this concept. It’s the foundation. #Symfony #PHP #BackendDevelopment #WebDevelopment #SoftwareArchitecture #Developers

11

Recently I've come across multiple cases where I thought that we could've known something before it happened. After some searching and looking through code, it seems Magento has a --dry-run command. This command does exactly what you probably already think it does; it analyses instead of running. `bin/magento setup:upgrade --dry-run=1` This gives you a `dry-run-instalaltion.log` in the `var/` directory of your Magento installation, which contains all the queries which were bound to run during the `setup:upgrade` command. Thankfully schema changes are forward, and Magento does not always drop important columns or tables. So you can safely run most of the queries ahead of time. Verify the file ofcourse and make sure to test versus a review environment. Thanks for coming to my M.Ed talk and be safe out there with your Magento installation.

23

2 коментарі

🚨 React Native Developers — Important Update! 🚨 ⏳ From November 1, 2025, all apps targeting Android 15 (API level 35) must support 16KB page sizes. ⚠️ No compliance = No Google Play updates! 👉 Action items to stay compliant: 1️⃣ Update React Native & Dependencies Upgrade to the latest stable React Native version. Ensure libraries, native modules, and dependencies are compatible with Android 15. 2️⃣ Review Android Build Configurations Check your gradle.properties and build.gradle for compatibility. Make sure your NDK/ABI configurations support 16KB page sizes. 3️⃣ Validate Native Modules If your app uses custom native code, confirm it compiles properly with 16KB page support. Rebuild and test any third-party native SDKs. 4️⃣ Test on Android 15 Emulators/Devices Run your app on Android 15 beta emulators or real devices. Look for crashes, memory issues, or ABI-related warnings. 5️⃣ CI/CD Pipeline Updates Update your build pipelines (GitHub Actions, Bitrise, Jenkins, etc.) to target Android 15. Automate compatibility tests to catch issues early. ✅ Taking these steps now ensures smooth Play Store releases later — and avoids last-minute fire drills. #ReactNative #Android15 #GooglePlay #MobileAppDevelopment #Compliance

2