Channel
Interviewed Person
Malte Ubl
We’ve been cooking something new—Remote Components. Imagine pushing a tiny change to your e-commerce site like updating a free shipping banner and having to wait hours for the entire site to build and test. That’s the reality of traditional monolithic frontends, where even the smallest updates can ripple across the codebase, slowing teams down and widening the blast radius for potential problems. Vercel is changing the game with micro-frontends providing an unmatched developer experience so far In this episode you’ll learn how Vercel micro-frontends implementation can: - Speed up build and deploy times - Reduce risks when releasing features - Empower teams to ship independently without stepping on each other’s toes =================================== Follow me for more tips! My gear: https://www.amazon.co.uk/shop/my50cents?ref_=cm_sw_r_cp_ud_aipsfshop_W744H9NEJG7C9T3JMFC2 Spotify: https://open.spotify.com/show/0W5YEY5T3ApuYS8H9I3DzL?si=c279c2df086b4d8f Twitter: https://twitter.com/lucamezzalira LinkedIn: https://www.linkedin.com/in/lucamezzalira Instagram: https://instagram.com/mezzalab TikTok: https://www.tiktok.com/@lucamezzalira
We've been we've been cooking. We we have a new technology. We call this technology remote components. We actually think there's a there's a really interesting intersection between Vzero and microphone ends. Before starting the episode, a word from our sponsor. Imagine you're working on an e-commerce site and you push a simple change to update the free shipping banner. Even though it was a small change, now you have to wait hours for the whole site to build and test to run. It's frustrating, but it feels necessary. In a typical
monolithic front end, even small, low-risk changes like this can ripple unpredictably across the codebase. As teams add more features, the build and deploy times get longer, and the blast radius for a potential problem gets wider. Teams step on each other's toes in staging. Minor bugs cause major outages, and updates slow to a crawl. It's not the features holding you back, it's the architecture. But there's a better workflow. Verscell is bringing you this season of microrends in the trenches. Later in this episode, you'll hear how modern teams are using
Verscell's microrend architecture to move faster, reduce coordination overhead, and deploy with confidence. Stay tuned. Welcome to a brand new season of Microontans in the Trenches, the podcast where we go behind the hype and we share with you stories from the trenches on how to scale your front- end architectures. My name is Luca. I'm your host. Today we have a very special guest. He was here last year and he was pitching to us how he was interpreting
the world of uh micro fronts and how it will be implemented inside uh their platform and I'm talking about Malta uh CTO of Versell and he's here to uh let's say share with us all the promises that made us last year. last year if you didn't watch the episode uh he was talking about having microns as first class primitives inside versel. So this time we'll see if uh he maintain his
promise. So welcome to M. How are you doing mate? Great. Thanks for having me. This is exciting starting a season with you and immediately going into the uh all the goodies that you are releasing with Versel. So uh tell us more. So last year you said first class primitive uh for microontent inside versel. Where are we? I did say that I remember um and we have been cooking. So I'm I'm I'm pretty excited where we with where we have
today and where we stand. So I I can explain what it means for Versel to have a first class primitive of of microins. So, Versell has this notion of a project which is basically a website, right? Um, and and a micro front end is in our world essentially composition of multiple projects into a multitude of of websites. And so, obviously, no one's stopping you from doing that, right? Like hand
rolling that composition um with all the tools that are available in the market. But what we've been building is that this form of composition of having effectively multiple applications into one is something that our platform understands. So very concretely what that means is that um I mean we love JSON files. So you put a microphone.json JSON file in your project and you essentially configure how the how this host app
composes out of multiple micro frontlets and there's a few insights we had along the way but um for now I'll just talk about user experience right so if you go into the versal dashboard it now knows that this is not just any projects this project is either composed into a different app to form a microphone in that way or this is the host and so it hosts all these other apps and you know it's just helpful that the platform