🎙️ The Commerce DevCast – Episode 5
Topic: Adobe App Builder
Guest: Alex Lyzun – Commerce Technical Team Lead at Comwrap Reply

In this episode, we explore Adobe App Builder – Adobe’s serverless microservice platform for extending Adobe Commerce with modern, scalable solutions.

Together with our guest Alex Lyzun, we discuss:

• • What is Adobe App Builder and how it works
  • Benefits like API-driven development & upgradability
  • Microservices, SaaS shift, and real-world use cases
  • B2B scenarios, testing, CI/CD, and performance
  • When App Builder is (and isn’t) the right choice

  ⸻

  🔑 Keywords:
  Adobe App Builder, Adobe Commerce, API integration, SaaS, software architecture, B2B commerce, UpBuilder, microservices, CI/CD, event handling, performance monitoring, community feedback

  📌 Key Takeaways:
  • API-based architecture with fewer core hacks
  • More control, but also more responsibility for dev teams
  • Good fit for specific use cases and integrations
  • Strong focus on performance, monitoring, and composability
  • Community support is critical to App Builder’s success

  ⸻

  🕒 Chapters:
  00:00 – Introduction to Adobe App Builder
  01:19 – Understanding the Architecture of Adobe App Builder
  05:26 – Differences Between Traditional Development and App Builder
  08:13 – Upgradability and Maintenance Challenges
  12:11 – The Shift in Responsibility for Upgradability
  16:23 – Testing and CI/CD in App Builder
  21:27 – B2B Use Cases and Customization Challenges
  27:20 – Unique Selling Proposition of Adobe App Builder
  33:55 – Consultation Over Development: The Key to Success
  35:50 – Choosing the Right Builder: Merchant Considerations
  38:15 – Evaluating Existing Systems: When to Transition
  40:03 – The Role of APIs in Modern Commerce
  43:54 – Understanding Adobe’s Ecosystem and Services
  46:39 – Practical Applications of UpBuilder
  49:14 – Architectural Insights: Composable Systems and Integration
  53:39 – Managing State and Performance in UpBuilder
  56:27 – Data Deployment Challenges in UpBuilder
  01:01:12 – The Role of Community in Adobe Commerce
  01:04:08 – Nuances of API Mesh Implementation
  01:08:55 – Performance Monitoring and Optimization
  01:12:55 – Challenges with API Compatibility
  01:15:02 – The Future of Adobe Commerce and Community Feedback
  01:25:18 – Summ-up

  ⸻

  👥 Meet the Hosts:
  • Vladyslav Podorozhnyi – https://www.linkedin.com/in/vladyslav-podorozhnyi
  • Oleksandr Kravchuk – https://www.linkedin.com/in/oleksandr-kravchuk
  • Vitalii Boiko – https://www.linkedin.com/in/vitalii-boiko-3ba269232

  🎙️ Guest:
  • Alex Lyzun – https://www.linkedin.com/in/nuzil

  Spotify: https://open.spotify.com/show/7ipQlNtjcGxQSXkqUKF5hg

  🌐 Visit our website: https://thecommercedevcast.github.io

  🔔 Subscribe for more episodes on Adobe Commerce, Magento, and eCommerce architecture!

  #AdobeCommerce #AppBuilder #eCommerce #Magento2 #ComposableCommerce #Microservices #AdobeSaaS #TheCommerceDevCast

🎙️ Frontend in E-Commerce: Headless vs Monolith – What Should Merchants Choose?

This episode focuses on one of the most important aspects of modern digital commerce: **frontend development**. We explore how frontend choices directly affect performance, scalability, and user experience. Should your e-commerce project go headless or stick with a monolithic approach? Our panel breaks down both strategies, compares real-world use cases, and gives practical advice for merchants.

🎯 Key Takeaways:

• - Frontend is critical for performance and conversion.
  - Merchants need technical guidance when choosing frontend architecture.
  - Monolith is great for simpler, cost-effective projects.
  - Headless offers flexibility and scalability for complex needs.
  - Performance optimization should be a top priority.
  - Accessibility and UX standards are increasingly important.
  - Hyvä themes provide a high-performing Magento alternative.
  - The right stack depends on traffic, budget, and team expertise.

  💬 Sound Bites:
  "A good frontend is about user interaction."
  "Hyvä was a game changer for performance."
  "Headless architecture offers more flexibility."

  📚 Chapters:
  00:00 Intro
  02:42 Why Frontend Matters
  04:30 B2B vs B2C UX
  07:05 Tech Choices in Frontend
  09:33 Aligning Frontend with Business Goals
  09:40 Types of Architectures
  11:54 Monolith vs Headless
  14:48 Current Tech Trends
  16:49 Where Frontend is Headed
  20:58 Tech Stack Navigation
  22:43 Choosing the Right Stack for Magento
  24:04 Working with ViewStorefront & Alokai
  28:09 Matching Frontend to Business Size
  30:11 Comparing Monolith and Headless
  38:02 Understanding Merchant Expectations
  48:08 Scalability Insights
  50:28 Architecture Evaluation
  53:16 Pros & Cons of Hybrid Setups
  55:32 Budget vs Dev Priorities
  57:24 Wrap-up

  🎤 Hosts:
  - Oleksandr Kravchuk → https://www.linkedin.com/in/oleksandr-kravchuk/
  - Vitalii Boiko → https://www.linkedin.com/in/vitalii-boiko-3ba269232/
  - Vladyslav Podorozhnyi → https://www.linkedin.com/in/vladyslav-podorozhnyi/

  🎙️ Guest:
  - Serhii Chernenko (Front-End Lead Engineer at Vaimo)
  LinkedIn → https://www.linkedin.com/in/serhiichernenko/
  YouTube → https://www.youtube.com/@serhii.chernenko

  🌐 More episodes & resources → https://thecommercedevcast.github.io/

  🔔 Subscribe and stay tuned for more e-commerce tech insights!

  #ecommerce #frontend #backend #scalability #monolith #headless #performanceoptimization #technologystack #userexperience #digitalcommerce

Together with our guest, Rico Neitzel (Co-founder and Lead Architect at run_as_root), we discuss the topic of Composable eCommerce.

Get ready to hear answers to questions like:

• • What is Composable Architecture?
  • What problems does it solve?
  • Who needs it?
  • What are the drawbacks and additional costs associated with this approach?
  • What are real-life examples of implementation?

  BONUS:
  A helpful checklist to determine whether Composable Commerce is a good fit for your business:
  https://www.run-as-root.sh/ccq

  Hosted by:
  • Vladyslav Podorozhnyi: https://www.linkedin.com/in/vladyslav-podorozhnyi/
  • Oleksandr Kravchuk: https://www.linkedin.com/in/oleksandr-kravchuk/
  • Vitalii Boiko: https://www.linkedin.com/in/vitalii-boiko-3ba269232/
  • Guest – Rico Neitzel: https://www.linkedin.com/in/rico-neitzel/

  0:00 Welcome!
  1:40 Introduction to Composable Commerce
  11:06 Understanding Composable Commerce
  17:14 Defining Composable Commerce for Merchants
  23:05 The Purpose and Problems Solved by Composable Commerce
  26:35 The Project Profile that fits Composable Architecture
  30:47 Examples of Composable Commerce Platforms
  43:40 Out-of-the-box Composable Commerce solutions
  48:38 Challenges of Composable Commerce
  55:35 Final Thoughts

Github Repo: https://github.com/vpodorozh/mcp-git-command-demo

Summary

In this session, Vladyslav Podorozhnyi introduces the Model Context Protocol (MCP) and demonstrates how to build an MCP server for executing Git commands. The conversation covers the importance of MCP in standardizing communication with AI models, the tools and resources it provides, and the process of creating and testing an MCP server. Vlad also discusses the architecture involving MCP, LLM, and client interactions, emphasizing the need for proper input and debugging to enhance functionality. The session concludes with a call for questions and further engagement.

Takeaways

• * MCP standardizes communication between applications and AI models.
  * It helps track conversations efficiently to avoid losing context.
  * MCP provides tools, prompts, and resources for developers.
  * Building an MCP server involves defining tools for specific commands.
  * Testing is crucial to ensure the MCP server functions correctly.
  * Connecting the MCP server to a client is essential for interaction.
  * Debugging is necessary to enhance the MCP server's functionality.
  * The architecture of MCP, LLM, and client is complex but powerful.
  * LLM acts as a decision maker in the interaction process.
  * Using MCP requires understanding and careful implementation.

  Chapters

  00:00 Introduction to MCP Server Build
  04:54 Exploring MCP Server Functionality
  09:16 Connecting MCP Server to Client
  12:31 Debugging and Enhancing MCP Functionality
  16:24 Understanding MCP Architecture and Workflow

  Author:
  Vladyslav Podorozhnyi https://www.linkedin.com/in/vladyslav-podorozhnyi

Together with our guest Oleksii Lunkov (Fractional Chief E-Commerce Officer), we explore how AI is changing the way we develop software. We talk about understanding requirements, how AI tools are making coding easier, and what this means for business goals, tech debt, and developer roles.

We also touch on:

• • The evolution of coding practices
  • The impact of AI on jobs and the future of work
  • The importance of evergreen skills
  • How to stay relevant in an AI-driven world
  • Procrastination and productivity in tech
  • What AI means for e-commerce development

  Hosted by:
  • Vladyslav Podorozhnyi: https://www.linkedin.com/in/vladyslav-podorozhnyi/
  • Oleksandr Kravchuk: https://www.linkedin.com/in/oleksandr-kravchuk/
  • Vitalii Boiko: https://www.linkedin.com/in/vitalii-boiko-3ba269232/
  • Guest – Oleksii Lunkov: https://www.linkedin.com/in/oleksii-lunkov/

Hosts: Vlad Podorozhnyi , Oleksandr Kravchuk , Vitalii Boiko

In this first episode of The Commerce DevCast, we introduce our show and share why we decided to launch it. You’ll meet the hosts — three experienced developers deeply involved in the Magento and Adobe Commerce ecosystem — and hear about our journey in eCommerce development.

We dive into:

• • The role of Adobe Commerce in today’s market
  • What Adobe App Builder is, how it works, and why it matters
  • Pros and cons of using App Builder in real projects
  • How it connects with other Adobe services
  • Key challenges around customization and cost
  • When App Builder fits — and when it doesn’t
  • The tools we use daily as developers
  • Introduction to Adobe SaaS and what it means for the future
  • And finally, how Adobe’s strategy is shaping the community

  Whether you’re a developer, agency, or merchant — this episode gives you a deep but practical look at where Adobe Commerce is heading and how to prepare for it.