4 ms·
microfront ends work well for self contained components that need to be used in multiple pages, they don't even need to have a "separate" backend, as long as th
by strikelaserclaw 4y ago
microfront ends work well for self contained components that need to be used in multiple pages, they don't even need to have a "separate" backend, as long as there is an area or code file for the backend code that deals with whatever data the microfront end needs.
- strix_varius 4y agoIn such a component-oriented circumstance, what is the motivation for choosing a “microfrontend” approach instead of, say, a component?
- weq 4y agoThe longer you are a developer, the more you see fads a cylic just like anything else in this world. rebranding happens every 5 to 10 years for most things.
- nevercomments 4y ago2008: Website with jQuery 2022: Server side rendering using island-based architecture for client-side rehydration of interactive components
- morelisp 4y agoPlease stop.
- collyw 4y agoWhat kind of component are you talking about? Could you give an example, because as a backend dev, I have no idea what sort of thing would require that level of separation.