<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Piotr Bletek on Medium]]></title>
        <description><![CDATA[Stories by Piotr Bletek on Medium]]></description>
        <link>https://medium.com/@p.bletek?source=rss-6dbd75795a27------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*lbYytIYz36jbBX5A9yqZxg.jpeg</url>
            <title>Stories by Piotr Bletek on Medium</title>
            <link>https://medium.com/@p.bletek?source=rss-6dbd75795a27------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 15:35:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@p.bletek/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Create your own Vue micro frontend architecture with VueMS library]]></title>
            <link>https://medium.com/ergonode/create-your-own-vue-micro-frontend-architecture-with-vuems-library-f054233b97cb?source=rss-6dbd75795a27------2</link>
            <guid isPermaLink="false">https://medium.com/p/f054233b97cb</guid>
            <category><![CDATA[pim]]></category>
            <category><![CDATA[nuxtjs]]></category>
            <category><![CDATA[micro-frontends]]></category>
            <category><![CDATA[ergonode]]></category>
            <category><![CDATA[vuejs]]></category>
            <dc:creator><![CDATA[Piotr Bletek]]></dc:creator>
            <pubDate>Sat, 18 Jul 2020 17:06:23 GMT</pubDate>
            <atom:updated>2021-03-25T07:01:27.303Z</atom:updated>
            <content:encoded><![CDATA[<h4>VueMS — a simple library to transform a monolithic Vue application into an application based on micro frontend architecture.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M5hVp52oCSYESiMt8Ly7ow.png" /></figure><p>Nowadays, the creation of a front-end project is simplified. We have a lot of help from the frameworks, which support us in many aspects of designing and building applications. The architecture of such solutions is already imposed and thoughtful, so it is enough to stick to certain rules and the construction of the project will go well.</p><p>Framework-based structures have a monolithic architecture, and unfortunately this kind of approach is not always suitable for our project. Sometimes instead of a typical monolithic application we need a more complex approach based on a micro frontend. I wrote about monolithic architecture and micro frontend in my <a href="https://medium.com/ergonode/microservices-approach-in-a-typical-vue-application-e07544b6f9a1"><strong>previous article</strong></a>, so here I won’t go into this topic.</p><p><a href="https://ergonode.com/">Product Experience Management Platform</a></p><p><a href="https://ergonode.com/"><strong>Ergonode</strong></a> is a project that has been directed towards micro service from the very beginning. The application is divided into backend part, which provides API and headless front-end part. Although backend division into microservices is quite a popular approach, it’s not exactly a front-end microservice. This approach is called micro frontend — not so popular, and not so easy to use.</p><p>While designing front-end applications we wanted to use <a href="https://vuejs.org/">Vue</a> and <a href="https://nuxtjs.org/">Nuxt</a> as our leading technologies and we didn’t really want to frame it into some overly complicated tools. We wanted to stay in one framework and keep the technologies in use to a minimum.</p><h3>VueMS process</h3><p>We collected all the technological and business requirements and on this basis we came up with an architecture concept that met all our objectives.</p><p>The first stage was to determine whether the application based on <a href="https://vuejs.org/">Vue</a> and <a href="https://nuxtjs.org/">Nuxt</a> can be expanded and divided into business contexts. Unfortunately, already at this stage we hit the wall. We were able to expand the application with small parts and fragments that complemented our application, but we could not completely separate the business context into a separate module. Nuxt and Vue allows you to add plug-ins, components and other smaller pieces, but does not allow you to separate whole pages and complex structures building the application from the pieces. We had a modular approach in our heads, which allowed us to expand the application in any way we wanted from completely independent pieces.</p><p>The next stage was to provide mechanisms that allow at the stage of implementation of the application to limit the modification of the modules’ cores and easy delivery and versioning of the modules. The implementation team should be able to install the application and connect any number of modules from any source. The teams should be able to overwrite the core modules with their own and expand the application in any way.</p><p>The only tool that will allow us to maintain independence of our modules, easy access and versioning was the <a href="https://www.npmjs.com/">NPM</a> platform. Thanks to the <a href="https://www.npmjs.com/">NPM</a> platform we can quickly find a package, install it in the blink of an eye, and package update is limited to update its version. The most important thing here is that the installed packages are unmodifiable.</p><p>Looking for a solution, we came across <a href="https://nuxtjs.org/guide/modules/">Nuxt mechanics</a> that allow us to extend the application with modules placed in <a href="https://www.npmjs.com/">NPM</a>, but such modules are quite limited. We decided to use this mechanism and based on it create a tool that would help us reach our destination. This is how the <a href="https://www.npmjs.com/package/@ergonode/vuems"><strong>VueMS</strong></a> library was created, meeting all our business and technology needs.</p><p><a href="https://www.npmjs.com/package/@ergonode/vuems">@ergonode/vuems</a></p><h3>VueMS operation</h3><p><a href="https://vuems.ergonode.com/"><strong>VueMS</strong></a> is a library based on <a href="https://vuejs.org/">Vue</a> + <a href="https://nuxtjs.org/">Nuxt</a> technology, which extends the mechanisms of these technologies and provides a completely new functionality, which is the micro service structure. All the mechanics and functionality of <a href="https://vuejs.org/">Vue</a> and <a href="https://nuxtjs.org/">Nuxt</a> are fully preserved and integrated with the new approach. Installation of <a href="https://vuems.ergonode.com/"><strong>VueMS</strong></a> does not impose changes but adds new possibilities. When building applications we can still use a monolithic structure and if we want we can use external modules. We can also completely move to a micro frontend structure and divide the application into separate business contexts as we see fit.</p><p>The modules can have a rconnection with each other or be completely independent, and all this depends only on the developers of the modules. Each module can act as a separate mini application that has everything that a monolithic application based on <a href="https://vuejs.org/">Vue</a> and <a href="https://nuxtjs.org/">Nuxt</a>. Modules can have pages with routing, independent components, plugins, and their own store (<a href="https://vuex.vuejs.org/">Vuex</a>).</p><h3>VueMS installation</h3><p><a href="https://vuems.ergonode.com/"><strong>VueMS</strong></a> was created for projects based on <a href="https://vuejs.org/">Vue</a> and <a href="https://nuxtjs.org/">Nuxt</a>, so these two technologies are essential for the library to work properly. Just create a project according to the instructions of these technologies and then install <a href="https://vuems.ergonode.com/"><strong>VueMS</strong></a> to the project.</p><pre>npm i @ergonode/vuems</pre><p>After installing the package in the project we have to add the appropriate configuration in the <a href="https://nuxtjs.org/guide/configuration">Nuxt configuration</a> file (<strong>nuxt.config.js</strong>) in <em>“buildModules”</em> section:</p><pre>buildModules: [<br> &#39;@ergonode/vuems&#39;,     <br>],</pre><p>These steps are enough for <a href="https://nuxtjs.org/">Nuxt</a> to start working with the <a href="https://vuems.ergonode.com/"><strong>VueMS</strong></a> library.</p><p>The most important thing is to properly configure the <a href="https://vuems.ergonode.com/"><strong>VueMS</strong></a> library, because without it the application will not work correctly.</p><pre>vuems: {         <br>  required: [             <br>   &#39;@ergonode/core&#39;,         <br>  ],         <br>  modules: {      <br>   local: [   <br>    &#39;@ergonode/dashboard&#39;,  <br>   ],  <br>   npm: [   <br>    &#39;@ergonode/core&#39;,  <br>   ],     <br>  },         <br>},</pre><p>Full configuration is described in <a href="https://vuems.ergonode.com/">VueMS documentation</a>, but here I will describe the most important settings needed to run the application. One of the key things we need to put in the configuration is a list of modules that we have in the application. List of modules is added in <em>“modules”</em> option in appropriate structure:</p><ul><li><strong>local </strong>— modules placed locally in the project. They are not hosted anywhere — the content of the modules is locally located in the project.</li><li><strong>npm </strong>— modules downloaded from the <a href="https://www.npmjs.com/">NPM</a> service — the content of the modules is unmodifiable.</li></ul><p>The names of the modules are directly related to their placement in the directory. Local modules are placed in the <em>“modules”</em> directory and are downloaded from it. Module naming is modelled on the <a href="https://www.npmjs.com/">NPM</a> service and based on the <a href="https://docs.npmjs.com/about-scopes">NPM scope concept</a>.</p><p>Another important option is <em>“required”</em>, which helps to determine which modules are required for the correct operation of the application. Required modules are often those that provide the base for building other modules and without them operation is impossible.</p><h3>Creating a module</h3><p>To properly create a module we have to stick to some rules, without which the module will not work properly. As a module can be any mechanism and its size is arbitrary, we can put any structure in it. A module can be a single component or a small plug-in, but also a huge functionality.</p><p>The structure of the modules is defined by the configurations of the <a href="https://vuems.ergonode.com/"><strong>VueMS</strong></a> library and can be changed. The default directory names are:</p><pre>export const DIRECTORIES = {<br>    assets: &#39;assets&#39;,<br>    components: &#39;components&#39;,<br>    config: &#39;config&#39;,<br>    layouts: &#39;layouts&#39;,<br>    middleware: &#39;middleware&#39;,<br>    pages: &#39;pages&#39;,<br>    plugins: &#39;plugins&#39;,<br>    store: &#39;store&#39;,<br>};</pre><p>When creating a module locally it is enough that we will place the directories in the main space, but when it comes to modules hosted in <a href="https://www.npmjs.com/">NPM</a>, all directories must be placed in the <em>“src”</em> directory.</p><p>For the module to work properly we need to add some things:</p><ul><li><a href="https://vuems.ergonode.com/module-config#indexjs"><strong>index.js</strong> file</a> — is needed for the Nuxt mechanism to properly load the module. It is located in the project main directory.</li><li><a href="https://vuems.ergonode.com/module-config#config-directory"><strong>config</strong> directory</a>— stores all possible configurations for the module. It must have an <strong>index.js</strong> file.</li></ul><h3>Summary</h3><p>By adding these configurations correctly, we are able to take full advantage of the application based on microservice architecture. All details related to the documentation are described <a href="https://vuems.ergonode.com/"><strong>here</strong></a>.</p><p><a href="https://vuems.ergonode.com/">Introduction</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f054233b97cb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ergonode/create-your-own-vue-micro-frontend-architecture-with-vuems-library-f054233b97cb">Create your own Vue micro frontend architecture with VueMS library</a> was originally published in <a href="https://medium.com/ergonode">ergonode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservices approach in a typical Vue application]]></title>
            <link>https://medium.com/ergonode/microservices-approach-in-a-typical-vue-application-e07544b6f9a1?source=rss-6dbd75795a27------2</link>
            <guid isPermaLink="false">https://medium.com/p/e07544b6f9a1</guid>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[micro-frontends]]></category>
            <category><![CDATA[ergonode]]></category>
            <category><![CDATA[pim]]></category>
            <category><![CDATA[nuxtjs]]></category>
            <dc:creator><![CDATA[Piotr Bletek]]></dc:creator>
            <pubDate>Thu, 16 Apr 2020 14:11:37 GMT</pubDate>
            <atom:updated>2020-04-16T14:11:37.759Z</atom:updated>
            <content:encoded><![CDATA[<h3>How can we transform a simple monolithic Vue application into a Micro Service approach?</h3><p>Over the past years, the approach to the development of frontend applications has changed significantly. Application development has been dominated by various frameworks like Vue, React, Angular. With the growing popularity of frameworks, the approach to architecture and production of such applications has also changed. Patterns and programming paradigms usually used in backend started to be adapted for frontend architectures. The transformation of the current frontend is drastic, but definitely this change has gone in the right direction.</p><p>The biggest flaw in framework-based applications is their monolithic structure. Such an application provides us with a specific solution that works great and solves the assumed business needs. Unfortunately, all this is closed in one indivisible application, in which everything is connected with each other and business contexts are not separated.</p><p>Fortunately, we already have a solution to this problem — we refer to the architectures called “Micro Frontends” and “Microservices”.</p><h3>Microservices &amp; Micro Frontends</h3><p>These architectures are such extensive topics that I have no intention of elaborating on their detailed functioning here. I just want to briefly explain the concepts and assumptions of this approach.</p><p>These two terms are very interrelated because both approaches focus on building modular architecture. This is an architecture made up of small parts that work together to provide a fully functioning solution. Such modules can be independent or have connections, which allows for logical arrangement of applications in context.</p><h4>Microservices</h4><p>This style of architecture is closely related to Service Oriented Architecture (SOA). This approach allows you to arrange applications from small modules that:</p><ul><li>divide applications into business contexts,</li><li>can be manufactured in small teams,</li><li>are easy to test and maintain,</li><li>are loosely connected,</li><li>are independently implemented.</li></ul><h4>Micro Frontends</h4><p>The concept comes from the architecture of “Microservices”, but is adapted to the frontend world. The idea of this solution is to treat the web application as a set of functionalities that can be shared between teams. The teams are independent and cross-functional and have the ability to choose the technology as they see fit.</p><p>This approach allows backend and frontend teams to share one independent business context and not worry about others.</p><p>Monolithic Frontends:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*JOnkkLLpbe6TCxnqc6zH8Q.png" /></figure><p>Micro Frontends:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*3NMHCNs33b7C7fWLCtn5WA.png" /></figure><h3>What we needed and why?</h3><p>“Micro Frontends” is a great thing, and certainly the use of this kind of architecture will bring many benefits when developing applications. However, sometimes we don’t have to use all the mechanics of the approach, because the project may have some limitations, the business model does not allow it, or possibly the choice of technology gives some limitations.</p><p>The <a href="https://ergonode.com/"><strong>Ergonode</strong></a> application is such an example. This is a PIM (Product Information Management) application, which is developed in an open-source approach. The project has a frontend and backend as separate running systems communicating through API. The backend used microservices from the very beginning, while the frontend, as it uses the Vue framework, had a typical monolithic structure.</p><p>Over time, however, business needs put us in a situation where the approach to “Microservices” architecture becomes one of the best solutions to meet all our assumptions.</p><h4>Ergonode assumptions:</h4><ul><li>Fully modular application — apart from functionalities created by the core team, we want to allow other developers to create their own modules extending the mechanisms of our application. It’s not easy, because you need to properly prepare the architecture for such extensions, not only from the backend, but also from the frontend.</li><li>Core of the application remains unchanged — extensions and modules do not affect the code written by the core team. Modules can use solutions already implemented, but they cannot modify them.</li><li>Module versioning — each module should be delivered in releasable versions. Customers should have a choice whether or not to upgrade a module, and the package update process itself should be very simple.</li><li>Simple module management — modules can be localised and hosted in external npm services. Installation and uninstallation should be a smooth process.</li><li>Stay with Vue — as the application was developed on the <a href="https://vuejs.org/">Vue</a> and <a href="https://nuxtjs.org/">Nuxt</a> frameworks, we want to continue using these technologies and not add any more unnecessary libraries if possible.</li><li>Simple addition of modules — a very easy process of creating a new module and smooth communication between the modules.</li></ul><h3>Solution</h3><p>All the problems and needs led us to a situation where we decided that the best solution would be to write our own library to help create “Microservices” architecture using <a href="https://vuejs.org/">Vue</a> and <a href="https://nuxtjs.org/">Nuxt</a> technology. This allowed us to stay with the technologies we used and not add new unnecessary frameworks. We decided to transform the written solution into a library npm, so that it could serve other companies facing similar problems.</p><p>That’s how the <strong>VueMS</strong> library was created.</p><p><a href="https://www.npmjs.com/package/@ergonode/vuems">@ergonode/vuems</a></p><p>Our solution is based on the built-in mechanism of <a href="https://nuxtjs.org/guide/modules/">Nuxt modules</a> in order not to modify the basic operation of the framework. The mechanism is closely related to Vue and was created only for this framework.</p><p>The main task of the library is to transform the monolithic approach to Nuxt architecture into a modular one. Of course Nuxt allows you to expand your mechanisms through external modules, but unfortunately they have their limitations. Often these modules are single components, directives, plugins that probably add mechanics to the system, and our need was more complex.</p><p>We needed each module to have a structure similar to a large application, so that its directory layout and mechanisms would not differ from a large monolithic application. More specifically, each module could have its own pages, its own routing, its own components, plugins and everything that every Vue + Nuxt based application has. The module would have no limits, so it could contain huge functionality as well as a single component or plugin.</p><p>These mechanisms allow for loading modules located locally in the project and modules downloaded from external services such as <a href="https://www.npmjs.com/">npm</a>. This allows you to version the modules and update them whenever needed. The packages hosted on the npm are thus resistant to modifications and only creators can change and update them. If a base module does not meet the customer’s expectations, it can be easily replaced by its own solution.</p><p>Communication between individual services was also an important element. We used alias mechanisms, thanks to which communication is simple and very clear. We also have the ability to determine which modules are required and whether the services have relations between them.</p><h3>Summary</h3><p>With this approach we can easily separate business contexts not only on the backend side, but also on the frontend side. The modules can be written by separate teams, which have separate tasks. The base application code is maintained and unchanged, and only the main team has the ability to modify it. The client’s instances are independent and can be easily expanded and the installation of finished modules is very simple.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e07544b6f9a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ergonode/microservices-approach-in-a-typical-vue-application-e07544b6f9a1">Microservices approach in a typical Vue application</a> was originally published in <a href="https://medium.com/ergonode">ergonode</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>