Temos visto significativos benef¨ªcios de se introduzir , que permitem aos times escalar a entrega de servi?os mantidos e implantados independentemente. Infelizmente, tamb¨¦m vemos muitos times criarem um mon¨®lito de frontend ¨C uma grande e confusa aplica??o de navegador que fica em cima de servi?os de backend ¨C, neutralizando fortemente os benef¨ªcios dos microsservi?os. Os micro frontends continuam a ganhar popularidade desde que foram introduzidos. Temos visto muitos times adotarem alguma forma dessa arquitetura como uma maneira de gerenciar a complexidade de m¨²ltiplas pessoas desenvolvedoras e times contribuindo para a mesma experi¨ºncia de usu¨¢rio. Em junho deste ano, um dos criadores dessa t¨¦cnica publicou um , que serve como refer¨ºncia para micro frontends. Ele mostra como esse estilo pode ser implementado usando v¨¢rios mecanismos de programa??o web e constr¨®i um exemplo de aplica??o usando React.js. Estamos confiantes de que esse estilo vai crescer em popularidade ¨¤ medida que grandes organiza??es tentam dividir o desenvolvimento de UI entre m¨²ltiplos times.
Temos visto significativos benef¨ªcios de se introduzir , que permitiram que times escalassem a entrega de servi?os mantidos e implantados independentemente. Infelizmente, tamb¨¦m vimos muitos times criarem um mon¨®lito de front-end ¨C uma grande aplica??o de navegador confusa que fica em cima de servi?os de back-end ¨C, neutralizando fortemente os benef¨ªcios dos microsservi?os. Os micro-frontends continuaram a ganhar popularidade desde que foram introduzidos. Temos visto muitos times adotarem alguma forma dessa arquitetura como uma maneira de gerenciar a complexidade de m¨²ltiplos desenvolvedores e times contribuindo para a mesma experi¨ºncia do usu¨¢rio. Em junho deste ano, um dos criadores dessa t¨¦cnica publicou um que serve como uma refer¨ºncia para micro-frontends. Ele mostra como esse estilo pode ser implementado usando-se v¨¢rios mecanismos de programa??o web e constr¨®i uma aplica??o de exemplo usando o React.js. Estamos confiantes de que este estilo vai crescer em popularidade ¨¤ medida que grandes organiza??es tentam dividir o desenvolvimento UI entre m¨²ltiplos times.
Temos visto benef¨ªcios significativos com a introdu??o de , que t¨ºm permitido aos times escalar a entrega de servi?os implantados e mantidos independentemente. Infelizmente, tamb¨¦m temos visto muitos times criarem um mon¨®lito de frontend ¡ª uma aplica??o para navegador grande e confusa sobre seus servi?os de backend ¡ª neutralizando os benef¨ªcios dos microsservi?os. Desde que apresentamos os micro frontends como uma t¨¦cnica para resolver essa quest?o, tivemos experi¨ºncias positivas com a abordagem e encontramos v¨¢rios padr?es para usar os micro frontends, mesmo conforme mais e mais c¨®digos migram do servidor para o navegador web. At¨¦ agora, contudo, os componentes web t¨ºm sido confusos neste campo.
We've seen significant benefits from introducing microservices architectures, which have allowed teams to scale the delivery of independently deployed and maintained services. Unfortunately, we've also seen many teams create front-end monoliths ¡ª a single, large and sprawling browser application ¡ª on top of their back-end services. Our preferred (and proven) approach is to split the browser-based code into micro frontends. In this approach, the web application is broken down into its features, and each feature is owned, frontend to backend, by a different team. This ensures that every feature is developed, tested and deployed independently from other features. Multiple techniques exist to recombine the features ¡ª sometimes as pages, sometimes as components ¡ª into a cohesive user experience.
We've seen significant benefits from introducing microservices architectures, which have allowed teams to scale the delivery of independently deployed and maintained services. Unfortunately, we've also seen many teams create front-end monoliths ¡ª a single, large and sprawling browser application ¡ª on top of their back-end services. Our preferred (and proven) approach is to split the browser-based code into micro frontends. In this approach, the web application is broken down into its features, and each feature is owned, frontend to backend, by a different team. This ensures that every feature is developed, tested and deployed independently from other features. Multiple techniques exist to recombine the features ¡ª sometimes as pages, sometimes as components ¡ª into a cohesive user experience.
We've seen significant benefit from introducing microservice architectures, which have allowed teams to scale delivery of independently deployed and maintained services. However, teams have often struggled to avoid the creation of front-end monoliths¡ªlarge and sprawling browser applications that are as difficult to maintain and evolve as the monolithic server-side applications we've abandoned. We're seeing an approach emerge that our teams call micro frontends. In this approach, a web application is broken up by its pages and features, with each feature being owned end-to-end by a single team. Multiple techniques exist to bring the application features¡ªsome old and some new¡ªtogether as a cohesive user experience, but the goal remains to allow each feature to be developed, tested and deployed independently from others. The BFF - backend for frontends approach works well here, with each team developing a BFF to support its set of application features.
We've seen significant benefit from introducing microservice architectures, which have allowed teams to scale delivery of independently deployed and maintained services. However, teams have often struggled to avoid the creation of front-end monoliths¡ªlarge and sprawling browser applications that are as difficult to maintain and evolve as the monolithic server-side applications we've abandoned. We're seeing an approach emerge that our teams call micro frontends. In this approach, a web application is broken up by its pages and features, with each feature being owned end-to-end by a single team. Multiple techniques exist to bring the application features¡ªsome old and some new¡ªtogether as a cohesive user experience, but the goal remains to allow each feature to be developed, tested and deployed independently from others. The BFF - backend for frontends approach works well here, with each team developing a BFF to support its set of application features.
