![\"Component-based](\"https:\/\/blogs.sw.siemens.com\/wp-content\/uploads\/sites\/21\/2023\/01\/Apvine-Component-Based-Architecture-1024x768.png\")
<\/figure><\/div>\n\n\nOf course, Mendix low-code<\/a> allows you to use a component-based architecture, which is part of what makes it such an agile and flexible tool. But more about that later. First, let’s define component-based architecture. In essence, it\u2019s breaking development down into a set of functionalities that you group together (into \u2018components\u2019), often with the intent to reuse as and when you need. A component could be a UI element, logic, data or many other parts that make up software development.<\/p>\n\n\n\n What does that really mean? An easy way to think about it is Lego. Whatever you\u2019re building (in the Lego-verse), it\u2019s mostly just a matter of finding the right building blocks – premade components – that can be reused and slotted in wherever needed without requiring a huge redesign or modifications to the whole. Each block is a stand-alone piece, a self-contained module that serves a specific function (of course, several blocks stuck together can then also become a component, albeit a slightly more advanced one). That\u2019s component-based architecture.<\/p>\n\n\n\n The traditional alternative to this is a scenario where every function and module is interconnected to the whole – everything built in one big stack as one complete application. By the way, micro-service architecture is not the opposite of component-based architecture. It is sometimes an example of component-based architecture, but not always.<\/p>\n\n\n\n As for the benefits of a component-based architecture, there are many depending on the specific use case, but here are some of the highlights:<\/p>\n\n\n\n To wrap things up, here are two examples of how we’ve benefited from component-based architecture in past projects at Apvine<\/a>. First, how it has created value for us internally. Once upon a time, while building an app for one of our lovely clients, we had a technical obstacle to overcome \u2013 accepting web socket communication (pushing data from the backend to the front end). We decided to create a specific component to do just that, and since then, we\u2019ve reused the little module countless times on various projects with various customers.<\/p>\n\n\n\n Secondly, how component-based architecture creates value for our manufacturing customers! While working on an Overall Equipment Effectiveness (OEE) application, we saw an opportunity to streamline the app for the client\u2019s benefit. By splitting up the OEE module into components for availability, scrap, performance and quality, they (and other companies too) were able to reuse them throughout multiple projects, streamlining development time and flow in the process.<\/p>\n\n\n\n And that\u2019s component-based architecture in a nutshell. Questions? Comments? Let us know!<\/p>\n\n\n\n Dennis Keldermans<\/a> and Dider Kerckhof<\/a> are working for Apvine and have extensive technical knowledge of component-based architecture and its benefits to your development team and your customers.<\/p>\n\n\n\nWhy we\u2019re fans<\/h2>\n\n\n\n
\n
Component-based architecture in action<\/h2>\n\n\n\n
About the authors<\/h3>\n\n\n\n
About Apvine<\/h3>\n\n\n\n