Micro Frontend Architecture Building an Extensible UI Platform by Erik Grijzen

Поделиться
HTML-код
  • Опубликовано: 25 авг 2024

Комментарии • 18

  • @manuelcardonaez
    @manuelcardonaez 3 года назад +4

    7:30 Our architecture
    17:20 Our implementation

  • @cliang1999
    @cliang1999 2 года назад

    really good presentation.

  • @MuhammedBasil
    @MuhammedBasil 3 года назад

    Well presented.

  • @AnandShiva94
    @AnandShiva94 3 года назад +2

    Really great presentation! Do you see webpack federation and yarn workspace making these things easier?

  • @Pandey_Ashish
    @Pandey_Ashish 3 года назад

    Really helpful!!

  •  4 года назад +2

    We do need something similar. Is the AppShell Open Source? I am interested how you solved the composition into the shell application.

  • @kishorekkota
    @kishorekkota 4 года назад +2

    Is the CLI ONLY designed for New Relic APM integration and building extensible UI ? I am interested in trying this out for a business application.

  • @pareenvatani9460
    @pareenvatani9460 4 года назад +2

    Well done :-)

  • @bensalehzainelabidine5221
    @bensalehzainelabidine5221 3 года назад +1

    Hello, the micro frontend must be applied for independent microservices, so if a micro front end has dependencies from another one it should be considered a bad case.....what about the User management microservices ??? all microservices depend on it because the user session is needed in all the next microservices....How to deal with the user management micro front end or this case is different ...Can someone please told us some explanation please ... And thank you very much

  • @Oswee
    @Oswee 4 года назад +6

    I think Web Components (LitElement) could play really nicely in this architecture because of encapsulation they provide.

    • @muh2k4
      @muh2k4 Год назад

      I didn't really enjoy Lit Components. Nothing beats having components in the framework (Vue, react, Angular, etc.) you are writing the app with. Starts with autocomplete, ends with using framework like features (e.g. v-model).

  • @carlocanlas
    @carlocanlas 4 года назад +1

    Is the nerdpack considered the micro-frontend package, or the nerdlet?

  • @GabrielKohen
    @GabrielKohen 4 года назад

    This is a great example on how it is done. I might move a bit on the team autonomy and take a bit of an initial hit on script loading to allow us to easily migrate UI frameworks as well as libraries which might be more difficult to do in a large company. Is there a chance that there is some sample code out there on GitHub for this project?

  • @chucknorris8351
    @chucknorris8351 3 года назад

    Stan Marsh is still searching for the CLI tool

  • @LonliLokli
    @LonliLokli 4 года назад

    Bit if user loaded the page he will not get any updated js & css 7ntil his browser be reopened, right?

  • @chenrvn
    @chenrvn 4 года назад +1

    Hey,
    1. Thanks a lot for this sharing
    2. when you bundle a Nerdlet - do u bundle also other nerdlet or you have a sophisticated build mechanism for delta (changes)?
    Thanks

  • @_yzt
    @_yzt 4 года назад

    How is that different from portlet architecture, which essentially does everything described in the talk?

    • @chchristomanos
      @chchristomanos 4 года назад +3

      It is not that different but it is native to the web platform. At the end of the day technology evolutions is not a straight line but a spiral where former ideas get revisited constantly