Hello, my name is Rebecca Parsons.

I'm here today for the ThoughtWorks podcast and I'm speaking to Cam Jackson and we're going

to discuss micro front ends.

Welcome, Cam.

Thanks for having me. And tell us a little bit about

yourself and how you got involved in front end technology and microfront ends in particular.

Sure. So I'm a developer here with ThoughtWorks. I've been working as a consultant for about five

years, a little over five years. I didn't join as a front-end developer, just as a developer consultant.

My first project was actually very infrastructure-focused, so no front-end work at all.

And then I sort of just fell into doing front-end work over the years, and that's what I've spent most of my time doing, and I certainly it. But I know I really think of myself as a full stack dev.

But yeah, probably what I've spent most of my time focusing on is the front-end world.

And I guess the work that I'm most interested in and proudest of is helping large organizations to scale their front-end development processes and

practices across many teams and across really complex products. Great. So what is a micro front-end

I mean, everybody's talking about microservices? Is it just microservice-ish stuff applied to front-ends?

What does it really look like?

There's certainly a lot of parallels to microservices. So I sometimes start by talking about that

because that's what more people are familiar with. I can give you a sort of a dictionary

definition that I use, which is that microfront-ins's an architectural style where independently deliverable

front-end applications are composed into a greater hole. So there's a couple of things in there.

There's the composition part of it, which is probably not that exciting. I mean, most UIs are

being built using composition as the main

sort of pattern for putting things together. Probably the more interesting part is that independently

...