Next.js future is distributed: how @VercelHQ is implementing micro-frontends with Malte Ubl

hi everyone today we have a super guest someone that can shed some light on how next we'll Implement Micon as a next fature uh today we have a person that is working for versel and he worked previously for 11 years in Google two and a half years work as CTO of verel so we have Mal UB hi Mt how are you very good it's very early here in California but uh I'm excited this thank you very much for uh joining

us and I'm sure the community will be super pleased to hear more about uh versel next microphone T what the future holds about that uh I give a very brief introduction about yourself if you can tell tell us a bit more about uh who you are what you do Etc would be great yeah absolutely you mentioned I was a Google for 11 years and the first kind of five years of my career there I worked in like very specifically front infrast

and the and obviously that kind of draws the line to my my role today and for sale but it's actually very very relevant what I did there for this podcast uh the my probably biggest achievement in hindsight is I created whiz which is the frontend framework that basically all consumer product that Google has made over the last 15 years or so um are built on and and and much of the older ones also have been backported so search Gmail like basically everything and recently it was

actually announced that this framework was is merging with angula so it's kind of out in the public it was it was entirely close Source until very very recently and the other thing that team did is it was the team that built the micro service architecture for Google and I would then move on and build the microfun infrastructure for Google in this time frame maybe 2012 13 14ish and which is now very widely deployed and you can imagine that

google.com is like this immense domain that has so many many different applications on it and then you have these like vertical things uh horizontal things like there's the What's called the one Google bar which the thing on top right like because there's this you know unified application navigation to that that spans all these apps so I've been like solving this problem for quite a while and and excited to to to get a chance now forel where it's kind of in a way I'm trying to do a similar job it's

just that my customers are not purely internal there the entire internet that's amazing I mean a lot of experience so for sure this uh interview would be super interesting for everyone so what's your point of view about micr frontend you as you said it's been a while that you're working uh with them so um what do you think about them uh do you think that are uh really helpful for companies nowadays especially uh large organizations msze organizations yeah I like so there's one principle for me in

software engineering which I I based on a quote from from Eric Schmid at the time CE of Google who would always say Revenue solves all known problems and I don't think that's true not certainly not true for Google today Revenue doesn't solve their antitrust problems but iteration velocity solves all know problem software problems like if you if you because as a professional you you

realize you cannot know the future but you can you know the professional thing then to do is to say okay but I can react to what I'm learning over time and so I have to iterate quickly and I think there is just a scale of software engineering that that you arrive at some point and not certainly not everyone's in there where having core scen splitting of applications broadly speaking is just something that's almost impossible to avoid and and so that's why I I kind of