Menu
Our team is developing a large project and we want to build a big app with multiple forms and dashboards and features. One monolithic SPA would get complicated. So we discuss the approach of „micro frontend“ architecture. The goal is to generate a parent SPA which contains several child SPAs. All SPAs should use the same framework: vueJS.
We found some implementations supporting this:
We want to use VueJS in our frontend (vue, vue-router, vue-resource, vue-loade, webpack)
730
Micro Frontends ArchitectureThe communication between these apps can be done with an event bus, window object, or publish/subscribe methods. Each app can be implemented by a separate team and any framework. Each app can talk to their backends or endpoints individually.
The result was Vue. js, which is one of the most popular frontend frameworks in use today.
VueJS is primarily used to build web interfaces and one-page applications. In saying that, it can also be applied to both desktop and mobile app development thanks to the HTML extensions and JS base working in tandem with an Electron framework – making it a heavily favoured frontend tool.
- Is it possible to create a composite UI (micro front end) based on vue by using standard vue tools?
Yes, it is possible. Pretty much any independent Vue-component you see published around (vue-select, vue-slider-component and even full "sets" of components such as vuetify, bootstrap-vue or vue-material are examples of reusable (composable) components developed using standard Vue tools.
- We have more than one page, so we need a solution to navigate from one side to another. How can we realize page transitions?
vue-router is the tool for this job. It is developed by the core team, so expect tight integration and great feature support.
- Is it possible to established a Event-Bus between the VueJS components?
Every Vue instance implements an events interface. This means that to communicate between two Vue instances or components you can use Custom Events. You can also use Vuex (see below).
- How can we implement a bidirectional communication between the components?
The best way to send data from parent component to child is using props. Steps:
props (array or object) in the child<child :name="variableOnParent">.See demo below:
Vue.component('child-comp', {
props: ['message'], // declare the props
template: '<p>At child-comp, using props in the template: {{ message }}</p>',
mounted: function () {
console.log('The props are also available in JS:', this.message);
}
})
new Vue({
el: '#app',
data: {
variableAtParent: 'DATA FROM PARENT!'
}
})<script src="https://unpkg.com/[email protected]/dist/vue.min.js"></script>
<div id="app">
<p>At Parent: {{ variableAtParent }}</p>
<child-comp :message="variableAtParent"></child-comp>
</div>You can also get references for Child Components (refs) and call methods on them.
Vue.component('my-comp', {
template: "#my-comp-template",
props: ['name'],
methods: {
saveMyComp() {
console.log('Saved:', this.name);
}
}
})
new Vue({
el: '#app',
data: {
people: [{name: 'Bob'}, {name: 'Nelson'}, {name: 'Zed'}]
},
methods: {
saveChild(index) {
this.$refs.myComps[index].saveMyComp();
}
}
});<script src="https://unpkg.com/[email protected]/dist/vue.min.js"></script>
<div id="app">
<div v-for="(person, index) in people">
<button @click="saveChild(index)">saveMyComp</button>
<my-comp :name="person.name" ref="myComps"></my-comp>
</div>
</div>
<template id="my-comp-template">
<span> {{ name }} </span>
</template>To communicate from child to parent, you'll use events. See demo below. There are also several modifiers that make this task easier.
var parent = {
template: '<div><child :content.sync="localContent"></child><br>At parent: {{ localContent }}</div>',
props: ['content'],
data() {
return {
localContent: this.content
}
}
};
var child = {
template: '<div>At child: {{ content.value }}<button @click="change">change me</button></div>',
props: ['content'],
methods: {
change() {
this.$emit('update:content', {value: "Value changed !"})
}
}
};
Vue.component('child', child);
Vue.component('parent', parent);
new Vue({
el: '#app'
});<script src="https://unpkg.com/[email protected]/dist/vue.js"></script>
<div id="app">
<parent :content="{value:'hello parent'}"></parent>
</div>Inevitably, though, as your application grows, you will have to use a more scalable approach. Vuex is the de facto solution in this case. Roughly, when using Vuex, you won't have to pass state around from parent to child: all of them will pick it up from the Vuex store (sort of a "global" reactive variable). This greatly simplifies the application management and is worth a post of its own.
Final note: As you can see, one great advantage of Vue is how easy you can prototype and test functionality. No build step, few abstractions over raw JS. Compared to other frameworks, I'd say this is an important bonus.
117
I have been curious looking for a quick way to implement the Micro-Frontend architecture. Some good resources I found are at:
However the problem I had with them is setup complexity. I like to see results pretty fast.
Piral.io (framework for portal-applications following microfrontends architecture) is still pretty much in development and it's mainly targeted for React (another JS frontend-framework).
I was able to come up with an approach and hope to write an medium article on that soon, however for the time being
/apps/:app_name) you can load sub-applications as appropriate. Within each sub-app, you can as well have a routing system in placeAbove approach works best if you want to:
13
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
