qoliber’s Post

One extension. Four extra features you didn’t ask for. Sounds familiar? It’s a recipe for bugs, performance hits, and security headaches. That’s exactly what 🥷Jakub Winkler, #qoliber and Jisse Reitsma 🇵🇸 🇺🇦, Loki Extensions and Yireo - unpack in the latest episode of the #MagentoExtensionQuality Podcast. “If you install something for one thing that you need and you get four other things on top of it… it could lead into bugs, performance issues, security issues…” ?? The answer? Single-purpose extensions. Even if that means running 100+ modules in your Magento shop because clarity beats clutter every time. “The Magento Core has been doing this for ages and we’re all fine with that.” ✅ More control ✅ Cleaner updates ✅ Easier debugging ✅ Better performance ?? Tired of mystery code creeping into your projects? Watch this episode and join the conversation on how we can raise extension quality across the ecosystem. 🎧 Full video in the first comment. #Magento #MagentoExtensions #MageOS #OpenSource #CleanCode #qoliber #Yireo #LokiCheckout #MagentoCommunity #MagentoPodcast #BuiltOnMagento

A Magento 2 and Adobe Commerce extension that provides a Model Context Protocol (MCP) server, automatically discovering REST API endpoints from Swagger schema and exposing them as MCP tools for AI assistants. Inspired by Sylius MCP Server Plugin: - Auto-discovers ALL API endpoints from Magento Swagger schema - Complete API coverage - every endpoint becomes an available MCP tool - Self-updating - new API endpoints become available automatically - Zero hardcoded API calls - everything generated at runtime GitHub: https://lnkd.in/dKheued4

🚀 Cloudrift now has a Web UI (Docker-based) Added a Web UI to Cloudrift to remove local install and setup friction. If you can run Docker, you can run Cloudrift. Same open-source core. Same drift and compliance logic. Just easier to get started and try. CLI for pipelines. Desktop for visual analysis. Web via Docker. Validate Terraform against live AWS using 21 OPA security policies, compliance framework mappings, and a visual resource builder. Open source & early — feedback welcome 👇 https://lnkd.in/gqHG8k2a #CloudSecurity #DevSecOps #OpenSource #Docker

🧠 Magento 2 Challenge Refactor This GraphQL Resolver You find complex logic inside a resolver. 📁 Model/Resolver/CartTotal.php The API works, but the logic is now duplicated elsewhere. Your challenge 🧩 Spot why the resolver is doing too much 🧩 Extract the logic into a service class 🧩 Keep the resolver as a thin orchestration layer Hint 💡 If logic can be reused outside GraphQL, it doesn’t belong in the resolver. #Magento2 #AdobeCommerce #MagentoChallenge #GraphQL #CleanArchitecture #BestPractices #DeveloperLife

SaaS Starters with Next.js 16 and Auth0 The blog post at https://lnkd.in/gHEFkD5t discusses SaaS starter kits built with Next.js 16 and Auth0 authentication. It likely covers setup for multi-tenant apps, leveraging Auth0's SDK for secure login flows. These templates help developers quickly bootstrap subscription-based projects with features like user management and API protection. Key Features Next.js 16 Integration: Uses the latest App Router, Server Components, and React 19 for performant SaaS apps. Auth0 SDK: Implements @auth0/nextjs-auth0 (v4+) for session handling, login/logout routes, and middleware protection. SaaS Essentials: Includes multi-tenancy via Auth0 Organizations, Stripe for payments, and database setups like Postgres. Setup Steps Clone a starter like Vercel's Auth0 SaaS template or Next.js examples. Configure Auth0: Add domain, client ID/secret, and scopes (e.g., read:users, create:organizations) in .env.local. Install SDK: npm i @auth0/nextjs-auth0, then wrap app with providers. Add middleware for protected routes and Actions for post-login logic like role assignment. This aligns with current best practices as of February 2026, with Auth0's Next.js SDK at v4.10+ supporting modern features. For the full post content, visit the linked URL directly.

Need to compress data directly in the browser but dread adding heavy libraries like pako to your bundle? Enter the browser's native CompressionStream API! Using new CompressionStream('deflate-raw') lets you compress data using the standard DEFLATE algorithm, completely dependency-free. What exactly is it? It's a built-in Web API that takes a stream of uncompressed data (like text converted to bytes) and outputs a stream of compressed binary data. The 'deflate-raw' format is particularly special: it gives you the pure, raw compressed payload without any extra zlib or gzip wrappers, maximizing your space savings. This is the exact magic that serverless applications use to store entire text documents inside a URL hash. You simply compress the text, encode it to base64, and suddenly a massive paragraph fits right into a tiny, shareable link. It's built-in, lightning-fast, and supported in all modern browsers. Next time you need client-side compression, skip the npm install and leverage the web platform! #compression #webapi #browser #frontend

I spent 2 days building a free tool instead of a SaaS. Here is why. I needed a quick way to inspect webhooks without signing up for a service or installing a local tunnel like ngrok. Existing tools were either paid, required login, or were too slow. So I built WebhookPro. It is a simple, open-source webhook inspector that runs entirely on Vercel's free tier. But the journey wasn't straight. 1. The Serverless Trap I started with an in-memory map to store requests. It worked perfectly on localhost. It failed immediately on Vercel because serverless functions are ephemeral. Every request hit a different instance. I had to rip it out and migrate to Upstash Redis. 2. The "Bleeding Edge" Mistake I decided to upgrade to Next.js 16 mid-project. Bad idea. Route handlers changed, `request.ip` vanished, and I lost 3 hours debugging async components. Lesson learned: Pick stable tech for quick builds. 3. The Windows Surprise Standard curl examples used single quotes `'`. This works great in Bash, but breaks in PowerShell. Since 50% of devs use Windows, copy-pasting my own example failed. I had to build a dedicated "Copy for PowerShell" feature. Why Free? Because everyone likes free stuff, right? It is free forever. No signup. No credit card. If you need to debug a webhook today, try it out: https://lnkd.in/d_2azaJd The code is on GitHub if you want to see how we handled the real-time polling: https://lnkd.in/dRmuWPuG #opensource #webdev #nextjs #saas #buildinpublic #developerexperience #webhooks

Hello everyone 👋 I recently built an ASP.NET Core Web API called Ecommerce Product API, focused on admin-level operations and external integrations. The idea is that platforms (for example, something like Swiggy) can call these endpoints to manage , Categories, products, users, and roles. While building this project, I focused on applying real-world backend practices instead of just basic CRUD. Tech & Architecture: • ASP.NET Core Web API (.NET 8) • Clean Architecture (Core, Infrastructure, API layers) • Entity Framework Core • JWT Authentication & Role-based Authorization • Custom Exception Handling Middleware • Serilog for structured logging • Swagger with JWT support • Docker for containerization • CI/CD pipeline using Azure DevOps Key implementations: • Centralized exception handling middleware • Secure authentication with JWT and role-based access • Proper dependency injection across layers • Structured request logging with Serilog • Dockerized the API for consistent deployments • Automated build and deployment with Azure CI/CD Main API modules: • Authentication & Users • Roles & User-role management • Products & Categories • Admin operations 🗄️ Database Design: The schema includes: • Users with unique emails and hashed passwords • Roles with a many-to-many User–Role mapping • Categories for product grouping • Products linked to categories with stock tracking GitHub Repository: https://lnkd.in/gGUvxQ9Y I’ll be sharing this project as a series of posts, where I’ll break down the architecture, authentication, middleware, database design, Docker setup, and CI/CD pipeline. Feedback and suggestions are always welcome! 😊 #dotnet #aspnetcore #webapi #backenddeveloper #cleanarchitecture #entityframework #jwt #docker #azuredevops #cicd #softwareengineering #dotnetdeveloper #learninginpublic

🚀 Excited to share my latest hands-on project! I recently architected and deployed a full-stack, enterprise-grade E-Commerce application. The main goal was to migrate a Spring Boot monolith into a fully distributed **Microservices Architecture**, and the results have been incredible! 💻☁️ Here’s a breakdown of the architecture: 🔹 **Microservices Pattern**: Decoupled the backend into 5 independent Spring Boot services (`api-gateway`, `user-service`, `product-service`, `order-service`, `payment-service`) utilizing Spring Cloud. 🔹 **Frontend**: Built a premium, highly-responsive Single Page Application (SPA) using React 18, Vite, and React Router to provide a seamless "Nike/Puma-style" user experience. 🔹 **Database**: PostgreSQL handles the persistent data (products, cart items) via Spring Data JPA and Hibernate. 🔹 **Containerization & Orchestration**: Every component is fully Dockerized and deployed into a custom Kubernetes (k3s) cluster. 🔹 **Networking**: Configured a Traefik Ingress Controller to route edge traffic intelligently to the Gateway and Frontend services. Building this end-to-end really solidified my understanding of distributed systems, container orchestration, and modern UI integration. You can check out the source code on my GitHub here: https://lnkd.in/gQNknq_m Always learning and building! Let me know what you think in the comments. 👇 #Microservices #SpringBoot #Java #ReactJS #Kubernetes #Docker #CloudNative #FullStackDevelopment #SoftwareEngineering #Tech #OpenSource