Road to Module Federation | Sumit Arora & Abdella Ali | ng-conf 2023

Summary

El guión de video discute los desafíos de una empresa que utiliza Angular y presenta la Federación de Módulos como solución para mejorar la escalabilidad, manutenibilidad y colaboración entre equipos. La Federación de Módulos permite dividir la aplicación en piezas más pequeñas, cada una desplegable de manera independiente, lo que mejora la experiencia del desarrollador y reduce el tiempo de mercado. Además, se explora la importancia de mantener la consistencia en la UI y la gestión de versiones de bibliotecas. Se destaca la necesidad de un enfoque estructurado y comunicación clara entre equipos para evitar la creación de silos y asegurar una arquitectura sólida y un buen proceso CI/CD para el éxito a largo plazo.

Takeaways

• 🤝 La **Modularidad y la Federación de Módulos** permiten separar la aplicación en piezas más pequeñas, mejorando la escalabilidad y la capacidad de despliegue independiente.
• 🚀 La **Implementación de Microservicios** y la federación de módulos pueden resolver problemas de rendimiento y mantenibilidad al permitir despliegues y actualizaciones incrementales.
• 🏗️ Un **enfoque arquitectónico sólido** es crucial para establecer límites claros entre las piezas de la aplicación y prevenir la duplicación de componentes.
• 👥 La **Colaboración entre equipos** es fundamental para el éxito de la federación de módulos y la microfinanzas, y se debe fomentar a través de una estructura de equipo adecuada.
• 🧩 La **Independencia** de los equipos permite una mayor autonomía y capacidad de toma de decisiones sin afectar otras partes de la aplicación.
• 🛠️ Un **desarrollo paralelo** es posible con la federación de módulos, lo que mejora la experiencia del desarrollador y acorta el tiempo de mercado.
• 🔧 La **Simplificación del proceso de pruebas y despliegues** se logra al permitir que cada equipo se centre en su propia parte de la aplicación.
• 🌐 La **Internacionalización** debe ser un aspecto global y consistente en toda la aplicación, no dejando espacio para que los equipos tomen decisiones individuales que puedan afectar la experiencia del usuario.
• 🔄 La **Gestión de versiones de librerías** se vuelve más fácil con la federación de módulos, reduciendo la complejidad en la administración de dependencias.
• 📚 La **Implementación de un sistema de diseño** compartido es esencial para mantener la consistencia en la apariencia y experiencia del usuario a pesar de la modularidad.
• ⚙️ Un **proceso CI/CD bien definido** es fundamental para que cada equipo maneje sus propios procesos de desarrollo y despliegue.

Q & A

¿Qué es la Module Federation y cómo puede ayudar a nuestra empresa?

La Module Federation es una técnica que permite dividir una aplicación en módulos más pequeños y autónomos, los cuales pueden ser desarrollados, mantenidos e implementados de forma independiente. Esto puede ayudar a nuestra empresa a mejorar la escalabilidad, la colaboración entre equipos, y la consistencia de la interfaz de usuario, al mismo tiempo que se abordan problemas de mantenibilidad y velocidad de lanzamiento.

¿Por qué nuestra aplicación actual tiene problemas de escalabilidad y mantenibilidad?

Nuestra aplicación tiene problemas de escalabilidad y mantenibilidad porque está centralizada en una única base de código, lo que hace que cualquier cambio requiera esfuerzos extensos y la colaboración de múltiples equipos. Esto provoca retrasos en el tiempo de lanzamiento y dificultades en la implementación de actualizaciones.

¿Cómo se relaciona la Micro Frontend con la Module Federation?

La Micro Frontend es un enfoque de desarrollo de aplicaciones web en el que la interfaz de usuario se divide en componentes más pequeños y autónomos, similar a cómo la Module Federation divide la aplicación en módulos. Ambas técnicas promueven la independencia y la capacidad de despliegue individual, lo que puede mejorar significativamente la experiencia del desarrollador y el rendimiento de la aplicación.

¿Qué desafíos podría enfrentar nuestro equipo al implementar la Module Federation?

Al implementar la Module Federation, nuestro equipo podría enfrentar desafíos como la configuración correcta de la arquitectura, la planificación adelantada para evitar conflictos, y la necesidad de establecer canales de comunicación eficientes para la colaboración entre equipos. También es fundamental mantener la coherencia en aspectos clave como la internacionalización y la gestión de estados.

¿Cómo la Module Federation puede mejorar la experiencia del desarrollador?

La Module Federation puede mejorar la experiencia del desarrollador al permitir un desarrollo paralelo en diferentes módulos de la aplicación, lo que reduce la posibilidad de conflictos y mejora la eficiencia. Además, al facilitar la implementación y el testing de módulos individuales, se agiliza el proceso de entrega y se reduce la complejidad en las operaciones de CI/CD.

¿Qué es un monorepo y cómo se relaciona con la Module Federation?

Un monorepo es una única base de código que contiene múltiples proyectos o componentes. Este enfoque se puede combinar con la Module Federation para facilitar la gestión de bibliotecas y componentes compartidos, mientras se mantienen los módulos individuales para un despliegue y desarrollo independientes.

¿Cómo se puede mantener la consistencia en la interfaz de usuario a pesar de la descentralización que trae la Module Federation?

Se puede mantener la consistencia mediante el uso de un sistema de diseño compartido y una biblioteca de componentes estandarizados. Esto asegura que todos los equipos sigan una guía de estilos y prácticas统一, a pesar de trabajar en módulos independientes.

¿Por qué es importante la comunicación entre equipos en el contexto de la Module Federation?

La comunicación entre equipos es crucial para compartir conocimientos, evitar la duplicación de esfuerzos y mantener una coherencia en la estrategia global de la aplicación. También permite un mejor seguimiento de los cambios y una mayor flexibilidad para adaptarse a las necesidades cambiantes.

¿Cómo la Module Federation puede facilitar la internacionalización de nuestra aplicación?

Al utilizar la Module Federation, se puede establecer un conjunto compartido de reglas y bibliotecas para la internacionalización, lo que asegura una gestión coherente y uniforme del idioma y la localización en toda la aplicación, evitando así la fragmentación y la incoherencia.

¿Qué tipo de arquitectura de desarrollo es adecuada para una empresa que busca implementar la Module Federation?

Una arquitectura que fomente la descentralización y la autonomía de los equipos, pero que también priorice la colaboración y la consistencia global, es adecuada para la implementación de la Module Federation. Esto podría implicar una estructura de equipo cross-functional y un enfoque en la comunicación y la planificación.

¿Cómo se puede demostrar el valor de la Module Federation a los miembros de nuestra organización que no están familiarizados con la técnica?

Se puede crear una demostración práctica con conceptos de aplicaciones que muestren cómo funcionan los módulos independientes y cómo se integran en una aplicación más grande. Esto ayudará a visualizar los beneficios de la Module Federation en términos de agilidad, escalabilidad y mejora de la experiencia del desarrollador.

Outlines

00:00

😀 Introducción a la Modulación y Federación de Módulos

El primer párrafo establece el contexto de la discusión, abordando los desafíos actuales que enfrenta una empresa ficticia con su aplicación. El CEO plantea preguntas a Abdullah, el CTO, sobre cómo mejorar la escalabilidad, la mantenibilidad y la colaboración entre equipos. Se introduce la idea de la Modulación y la Federación de Módulos como una solución para estos problemas.

05:01

🧐 Desafíos y Oportunidades de la Federación de Módulos

Este párrafo explora cómo la Federación de Módulos puede ayudar en la escalabilidad y la independencia de los módulos dentro de una aplicación. Se discuten las ventajas de la desacoplación de las preocupaciones y la creación de límites claros entre las piezas de la aplicación. Además, se destaca la importancia de la colaboración entre equipos y cómo la Federación de Módulos puede facilitar el desarrollo en paralelo.

10:01

🤔 Consideraciones para la Colaboración y la Cohesión

El tercer párrafo se enfoca en la importancia de mantener la colaboración entre equipos a pesar de la modularidad. Se sugiere la creación de límites claros para entender qué es responsabilidad individual y qué es de consideración holística. Se discute la necesidad de mantener una biblioteca de componentes compartida y un sistema de diseño para asegurar la consistencia en la aplicación.

15:03

📚 Internacionalización y Consideraciones Globales

Este párrafo aborda la internacionalización y cómo la Federación de Módulos puede manejar la creación y el mantenimiento de una aplicación multilingüe. Se destaca la importancia de tener una consideración holística y una gestión adecuada de las bibliotecas y reglas compartidas para evitar problemas de consistencia y compatibilidad.

20:05

🛠️ Implementación de la Federación de Módulos y Retos Adelantes

El último párrafo discute los desafíos y pasos para implementar la Federación de Módulos. Se mencionan posibles riesgos y la necesidad de una planificación adecuada, la elección de tecnologías consistentes y la formación del equipo. Se ofrece una metáfora de la transición de un edificio a una ciudad de edificios para ilustrar la flexibilidad y cohesión que se busca con la implementación de la Federación de Módulos.

Keywords

💡Modularidad

La modularidad se refiere a la capacidad de dividir un sistema en partes independientes o módulos que funcionan juntos. En el video, se discute cómo la modularidad puede ayudar a mejorar la escalabilidad y la manutenibilidad de las aplicaciones, permitiendo que diferentes equipos trabajen en partes separadas del proyecto sin afectar el resto.

💡Microservicios

Los microservicios son una arquitectura de software en la que un aplicación se compone de pequeños servicios que se desarrollan, se implementan y se escalan de manera independiente. En el contexto del video, los microservicios son un enfoque que se menciona para resolver problemas de escalabilidad y mantener la consistencia en la UI.

💡Federación de Módulos

La Federación de Módulos es una técnica que permite a los módulos de una aplicación web interactuar entre sí de manera independiente. Se destaca en el video cómo esta técnica puede mejorar la independencia de despliegues, lo que es crucial para el tema principal de la discusión.

💡Despliegue Independiente

Un despliegue independiente implica que cada módulo o parte de la aplicación puede ser actualizado y desplegado por sí solo sin afectar el resto del sistema. En el video, se discute cómo esto puede mejorar la experiencia del desarrollador y la agilidad en el lanzamiento de nuevas características.

💡Escalabilidad

La escalabilidad hace referencia a la capacidad de un sistema para manejar el crecimiento en el número de usuarios o la cantidad de trabajo sin degradar el rendimiento. El video explora cómo las técnicas de modularidad y federación de módulos pueden mejorar la escalabilidad de las aplicaciones.

💡Manutención

La manutención de software se refiere a los esfuerzos continuos para mejorar y corregir un sistema existente. En el video, se menciona que la aplicación actual tiene problemas de manutención, y se busca soluciones que faciliten el proceso de realizar cambios sin afectar negativamente al sistema.

💡Colaboración entre Equipos

La colaboración entre equipos es esencial para el éxito de cualquier proyecto de desarrollo de software. El video aborda cómo la falta de colaboración puede afectar negativamente al rendimiento y la calidad de la aplicación, y cómo las prácticas de modularidad pueden mejorar la situación.

💡Consistencia de la UI

La consistencia de la interfaz de usuario (UI) es importante para la experiencia del usuario final. En el video, se discute cómo la falta de consistencia en la UI puede ser un problema y cómo las estrategias de diseño y arquitectura pueden ayudar a mantener una apariencia y funcionalidad coherentes en toda la aplicación.

💡Desarrollo Paralelo

El desarrollo paralelo permite que múltiples equipos trabajen en diferentes partes del mismo proyecto sin interferirse mutuamente. El video destaca cómo la federación de módulos puede facilitar el desarrollo paralelo, mejorando la eficiencia y la velocidad de entrega.

💡CI/CD

CI/CD son las siglas de Integración y Despliegue Continuos, prácticas que automatizan el proceso de prueba, integración y despliegue de código. En el video, se discute la importancia de tener un proceso CI/CD sólido para apoyar la arquitectura modular y el desarrollo ágil.

💡Internacionalización

La internacionalización es el diseño de un software para que sea capaz de soportar diferentes idiomas y regiones sin necesidad de hacer cambios en el código fuente. En el video, se aborda cómo la internacionalización es un aspecto clave que debe ser manejado de manera holística en lugar de dejar la decisión a equipos individuales.

Highlights

The discussion introduces the concept of Module Federation as a solution to scalability and maintainability issues in large applications.

Module Federation allows applications to be broken down into smaller, independently deployable parts.

The approach can improve performance and provide better control over the application's architecture.

Microfrontends enable teams to work in parallel, reducing the complexity of managing a single large codebase.

The CEO and CTO discuss the challenges of frequent releases and the lack of collaboration between teams in the current setup.

Consistency in the user interface is a concern, and Module Federation could help standardize components and design.

The CTO suggests that microservices and Module Federation can lead to more autonomy for teams while maintaining a unified application experience.

Developer experience is considered, with the potential for parallel development and reduced risk of breaking other parts of the application.

Independent deployments can lead to faster time to market, which is crucial for competitiveness.

The conversation addresses the potential complexity introduced to the development process but argues the benefits outweigh the costs.

Cross-team collaboration is emphasized as essential for the success of a modular application architecture.

Component libraries and shared contracts between microservices are highlighted as a means to maintain consistency.

The importance of a shared design system for maintaining a unified look and feel across different parts of the application is discussed.

The CTO proposes a clear boundary between individual team considerations and shared organizational concerns.

The potential benefits of monorepos in conjunction with Module Federation are explored.

Internationalization is identified as a global concern that should be managed consistently across all parts of the application.

The need for a clear plan and the right tooling to enforce consistency in a modular architecture is emphasized.

The CTO presents a proof of concept application to demonstrate the practicality of Module Federation.

The CEO is convinced by the potential benefits and the discussion concludes with a call to action for the organization to start implementing Module Federation.

Transcripts

foreign

[Music]

to take you on the road to module

Federation and talk about some of the

challenges and aspects of of that

so to give you a background I know it

has been long day for you all and you

have been going through a lot of angular

sessions these days so we are going to

this uh discuss about

we're going to take this talk and

discuss about the module Federation

amongst us

and going back and forth about the

aspects of module Federation between me

and Abdullah

to get started uh we are going to assume

that we both work in an awesome

Enterprise working with an awesome

angular angular framework itself I'm

going to assume the role of a CEO of the

company and ask the tough questions to

CTO Abdullah asked me and who is going

to answer all of them

like as you know we have been uh having

a lot of issues with our application

application uh doesn't scale well and

it's having maintainability issues even

to do a small change we to do a lot of

stuff

um but to stay competitive we have to do

a releases so often and also the

collaboration between teams is lacking

uh the UI is not consistent so what do

you think we can do uh to resolve all

these issues

yeah that's a that's a tall order it's a

long list of things that are kind of uh

challenging us right now but you know

what I've been looking into some things

and I think there's something we can do

that can solve quite a few of these

problems so have you heard of

microfinance

probably a little bit Yeah more recently

though

module Federation

in tandem I think we have the exact

formula to solve our problems

now

what is all of that what is microphone

and what are microphones what are what's

modular Federation well to summarize it

in a really quick simple way imagine it

as a system in which you can kind of

separate out your concerns break up your

application into smaller pieces and

allow you to have independently

Deployable parts of your application

working in tandem working in parallel uh

to give you a holistic overall

experience while also being performant

that that really came in with multiple

Federation and uh giving you some

finding control as well

so

what I mean by independent deployments

are modules so

right now our app is struggling here we

have we have this one pipeline we have

this one narrow pipeline it feels like

we releases every two months and six

weeks of those two months is planning

out the next release it is a pain in the

butt and we have like 100 people we have

10 teams all working the same code base

all jocking to get all their features

out some nice long change log of 100

things that we all to test and you know

make sure it's all working right and get

through all the environments and then

something goes wrong one of those little

lines has a little issue roll back the

whole thing and add a couple weeks to

the release and repeat I think this is a

pain that we felt for a long time and I

really want to find a way around this

problem now I think this is a thing we

can solve with a good strong

architecture around microponense and

modularation now this is a holistic

thing it's not just about you know

architecture it's about like you know

mentality as well too it's about our

team structure it's about our components

and our architecture around that as well

too we don't do reasonable components we

try we try our best we've tried a couple

times okay but it always happens you

know somebody will take a component

they'll move it into that part of the

application they'll put in some very

context specific code in there that

won't work with somebody else's part of

the application and it all fall apart so

they make our own copy of that and then

we have five versions of that component

and it's all messy it's all gross it

doesn't ever work out it'd be great if

we had a nice strong boundary between

our application pieces and the Clones

themselves and we can have a nice strong

clear expectation as to how this should

be used and how this will be brought

into our application I think we can do

that with microfinance and you know this

sounds like I'm trying to be really kind

of a tyrant about how things have you

done and I think that's kind of the

problem that people feel right now ready

we want to make sure that our teams

individually feel autonomous like they

can make their own choices about a lot

of the application without worrying

about

um updating a version of a library

that's depending on and then breaking

another part of the application the

teams using the same Library it happens

all the time we hate it everyone hates

it how can we get around that

I think overall this is kind of this

discussion around the coupling concerns

and decoupling kind of context

decoupling pieces of our application in

a way that is still providing a nice

strong underpinning a framework that

connects them all

um that sounds promising uh but how does

module Federation help in scalability as

swapping a single Lego block from a

structure is a not that trivial and

that's one of the challenges that we are

facing as an organization

yeah yeah it really is it's really hard

I think even if we tried our best it

would not be easy this is going to take

effort it's going to take concerted

considerations I mean

there are so many things to consider but

in those considerations we also

potentially have opportunities like one

thing I I like about

microfinance and model Federation is

something as simple as being able to put

your entire

micro app into its own folder

independent from everything else

conceptually mentally visually you see

this as a little block of code in fact

if you really wanted to you could put

this into its own repository and have it

be completely separate you know you have

options here you can do a couple things

but the fact that you have those options

are fantastic and I think that it really

again aligns with the separation of

concerns when you can create those

boundaries in your application you can

create things like

incremental updates where you worry

about updating individual parts of your

application your change logs aren't 100

items long for the whole application

they're tied to specific parts of your

application small tiny pieces it gets

much easier to give you those quick

incremental updates that I think we're

all trying to move towards right now and

this sounds hard to do and it is and one

of the things we have to do is make sure

that we keep and maintain important

parts of our application and our

organizations uh strengths cross-team

collaboration is an essential part of

that if we're not collaborating across

teams and we kind of Silo each other all

of ourselves off into our own little you

know towers and we ignore each other

we're gonna have a lot of problems so

creating a good framework for crossing

collaboration and communication is

essential for having success with

anything like this

so it means we can break our application

into smaller modular applications and

Each of which can be maintained and

developed individually

but

how about the developer experience right

aren't we complicating things by

breaking a single application into more

modular applications that needs to be

maintained and released individually

yeah yeah there's no there's no for your

lunches out there you know we might be

complicating things quite a bit here you

know there is Simplicity in that single

Focus repository with everything's

inside of there

but

at least in our cases it's not it's not

helping us out

um we have to kind of move away from

that at least for now or let's explore

some other options and you know while we

do kind of hurt developers in some ways

that way if we're not careful we give

them a lot of options my favorite thing

I'm looking forward to more than

anything else is a nice clear easy path

to parallel development when you're

going to have

all 10 teams working in their own pieces

of code without worrying about you know

am I going to break you know products am

I going to break user application Pages

I'm going to break the footer who knows

right they're all separate they're all

they're all removed and that

Independence allows for independent

deployments everywhere from the

development all the way up to deployment

and that's that's great for faster time

to Market we can really make sure that

we can get everything out the door

quicker we have to worry about getting

the whole Beast out the door at the same

time squeezing through that tiny little

door I think that this is all a part of

a better user experience and sorry a

better developer experience developers

care about the stuff they care about the

faster time out the door the passive

deployments they get bogged down by

those release processes as much as

everybody else does so making sure that

we can simplify that we'll make things

better and simplify things like testing

when you can test only your part of the

application you can worry about testing

Suites that solve your particular

problems and not all problems for all

parts of your application and

this all gives you this individualized

pipeline you can have different CI CD

pipelines for each release and in fact

if you really wanted to you could

have a release with all 10 go at the

same time and if only one of those apps

breaks roll that one back don't have to

worry about everything else breaking

that's the kind of Independence and and

durability you can get

all with a faster deployment process

well I think that's what we need to move

fast without mitigating the risk

but

if everyone is working on their own

application aren't we compromising on

the team collaboration because everyone

can work on their own application and

have different patterns and

architectures between

individual apps instead of the whole

organization itself

yeah I mean that's entirely true you

know we run the risk if we're not

careful of creating these teams that are

just completely removed from each other

finding ways to to get ahead of them is

important like ironically I think one

thing we can do is create a clear

boundary and just understand exactly

what is individualized consideration

what is a you're part of your title app

and what is a holistic overall share

consideration one is to be I think I

everybody in the entire team the entire

organization sits down and talks about

and what only needs the five six seven

people on your team to talk about

creating that boundary gives you the

opportunity to collaborate in different

ways more comfortably you don't have to

be in every single meeting you can be

the only things that matter to you and

you have a good idea as to what matters

to other people as well too because you

have those boundaries when you don't

know you you assume everybody needs to

be there all the time right how many

meetings are you invited to that you

absolutely do not be need to be

so we have other things we can do to

kind of give us that consistent look and

feel too we don't want to lose

consistency in our application

library is a big part of that you know I

mentioned our components are not great I

think we're moving it out externally

gives us lots of opportunities and

benefits we can have better consistency

when we really consider components as a

big part of that underlying shared

architecture that overarching piece to

give us the sort of uh

architecture the the pipes the the

plumbing the electricity for our overall

application and while we do all of this

stuff we can still give people the

flexibility to decide how their teams

individually can behave you know that's

a really big Challenge and finding that

balance is really important we don't

want to have teams feel like

they have to fall in line toe the line

all the lines to make sure that they

don't you know rock the boat too much

they can do what they want to do to some

degree to you know explore experience

and and push things forward

um as long as we have the right

architecture to kind of support those

efforts and have a shared effort as well

and like I said between all of this we

need to have improved communication we

need to create clear guidelines for how

we can keep it about certain things if

it's a shared consideration do we have

the right channels communicate across

those I don't think we do right now I

think everything is kind of global

things need to be kind of considered in

their own hierarchies in that regard

so that's great with everything in place

uh teams can collaborate and share

components between each other but still

like they can share the contracts of the

components between each other but still

can design each of these components

differently giving users a bad user

experience

yeah that's a good point I mean you can

take a photo down from the library and

do whatever you want to it and inline

style it whatever you want we need to we

need to consider how we want to

kind of Architects are designed with

everything else a design system is a big

part of what I think we need to do going

forward it's not just about having

components that are shared it's about

having styles that are shared it's about

having processes and ideals that are

shared fundamentally and that covers uh

such a wide range of topics that you'd

be surprised so having having this idea

of exactly what is shared and not shared

it doesn't just mean code doesn't just

mean even CSS it means conceptually what

do we want to consider as a team versus

individuals and design and consistency

is a big part of that

and when we talk about user experience

we have to consider not just

visualization in ux performance as well

too if we're going to move towards uh

modular Federated system micro front end

that's a big part of what we can

potentially risk if we're not careful

but if we do it right we can have

fantastic opportunities especially with

multiple Federation they really resolve

some of the issues that came out across

with micropriators in the past things

like Library versioning becomes much

easier to manage and we have some

flexibility there too we can even do

things like mono repos with much

Federation and microfinance you can mix

them all together and do all kinds of

cool things

and like I said you know we need to make

sure that our teams have the opportunity

to communicate with each other when we

can have

ux communicate with the back end team

communicate with the front-end developer

all together all of their own

performance considerations can be

communicated in a clear way so I think

this is one of the nice things about

having a smaller team it's really hard

to do that when you have huge teams

where everyone's kind of stressed all

the time I really loved and miss the

days of our smaller company when we had

everyone on the same table talking about

things and sharing and and communicating

we can get some of that back with the

right team structure and all of this all

of this is dependent upon having a good

CI CD process we need to think about

that very clearly and make sure we

decide how each team owns processes and

thinks about their development

employment it's not no longer a separate

concern each team considers that

separately okay uh so it seems like

model Federation can solve a lot of our

issues that we are facing right with

independent deployments and all that's

done but one last question

what about internationalization right

you know our application is being used

by users of different regions and we

have multiple languages how do we solve

around that

yeah you know I think

I think when we think about things like

internationalization

um it's a great example of one of those

things that we really don't want to have

individual teams making very important

decisions for it's a great example of

something that should be holistically

across the application consistent If We

Had Each team for example using a

different

i-18n library and they have different

rules for either handle things like

pluralization that could be a problem

but if we have a shared set of rules and

a shared hierarchy of of asset sharing

for example we can really create the

right pipeline to not get in each

other's way but also ensure that we are

using things to really benefit each

other and to benefit the application as

a whole we need to make sure that we we

um we enforce consistency through

the tooling itself and not through kind

of browsing people and you know there

are a lot of things that should be

globally considered this way not just I8

and N State Management maybe even Global

error messaging there's probably quite a

few things that fall into the same

category so you're right I think I eat

and internalization is an important

thing that should be a global

consideration and we need to make sure

we have a list of all those important

things and a clear plan for how to

handle them

okay that sounds quite interesting but

implementing the module Federation isn't

it that hard like we might end up taking

that effort and implementing a lot of

stuff uh without getting or seeing any

tangible benefits in

yeah it's it's not it's not going to be

easy

um there are risks involved you know

there's the first one right away is if

you've ever tried to set up a

microfinant or any sort of like

complicated multi-team architecture you

have to make sure your configurations

are set up correctly is to make sure

that you really plan out in advance

otherwise it's just gonna be a lot of

pain off the bat luckily things are

getting easier now there's a lot of

great guidelines on how we can handle

different kinds of architectures that we

might want to consider uh to solve our

particular needs so making sure that we

really have a good idea on what we want

in that regard is important and making

sure we have the right consistent

Technologies to use as well too if we

want to have a shared we want a library

or have a shared

um I can end Library whatever it may be

that we don't want to have be different

across applications that can be clearly

set and specified and different

architectures can even enforce this like

I mentioned if we want to have a mono

rebuild architecture we can have more

specification that's exactly how we want

all of our libraries and all of our

teams rather to share their libraries

and yeah like this doesn't require

training it's gonna require alignment it

doesn't require performance optimization

can require so many different things but

the effort is worth it

okay well that's quite a big task and I

trust you with that uh so can you can

can you summarize all of this uh again

to me so that uh we can talk to the

organization and come everyone on board

and start implementing that quickly

okay okay let me try let me try to

summarize this in a nice

absorbable way imagine right now we are

working in this one giant office

building

and you know we're all staff we're all

maintaining we all work in it and we

want to change the lobby if three teams

want to do that they have to wait in

line one of the other you can't have

them all in there at once let's say

somebody pulls a fire alarm everybody in

the building has to leave all at once

you create these dependencies that maybe

you don't necessarily want to have

um but what if you had more of a sort of

city with multiple buildings all working

individually but still sitting on top of

the same infrastructure we have to

decide what that looks like we said you

want to share gas electricity water

services like

firefighters and all that stuff but once

we have a clear plan for what is shared

and what is individual we can create

systems that are really going to provide

the flexibility to allow people to

individually deploy their buildings

whenever they want to individually have

the flexibility and to have the

creativity to to get their buildings

their own individual Flair while still

giving a consistent look and feel

through a design system kind of like

having the same architecture to all the

buildings the same bricks that you have

to use the same Granite whatever it may

be find a good way to create these

contracts between all of our teams is

going to give us everything we need to

give us a beautiful city while hiding

all the wires underground let's say

it's quite interesting I

sure I can convince uh everyone uh to

start working towards that but it will

be really handy uh if you can show

something to us

all right cool have a quick prove a

concept apps I've been working on real

quick but I hope they give us a good

idea of how this works if I can move my

mouse in the right way let's see uh okay

here it goes

uh okay

I feel like I'm doing surgery right now

[Laughter]

am I mirroring I am mirroring

I do this first perfect and

all right yes

I'm done happy with that right there but

we have a nice little app and you know

we had this little outline to kind of

highlight that these separate pieces are

actually

um their own little micro apps you can

have the structure all in one page looks

nice and simple looks the same and you

know little links here for example click

on to Do's I have my tutors right there

they just popped right in but what if I

wanted to see that individually without

the whole out there at once well I just

had to go to localhost

think it's three thousand now one

yes that's where it was and you can see

it's its own application by itself

this allows us to have our individual

yeah

our individual micro applications

considered thought of view tested

without worrying about the whole

application but it comes together in a

nice beautiful app when it's all done

right

that's good that's great right okay

um I think that

I am convinced that module Federation is

where to go for our organization uh

and clear about that

so thanks everyone thank you thank you

if you have any questions just come talk

to us at our booth

thank you thanks again